[LU-6671] Wireshark: LDLM_ENQUEUE reply with undecoded buffer

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.11.0
• Labels: wireshark
• Severity: 3
• Assignee: Nathaniel Clark
• Reporter: Andrew Uselton (Inactive)

Description

The attached file is the tcpdump on a client where I ran a "truncate" test ('multiop <file> OTc 1024'). After the MDS_REINT request and reply there is an LDLM_ENQUEUE request and reply for an extent lock. The "verbose" tshark output shows in the header that there are three buffers:

Lm Buflens: 152
Lm Buflens: 112
Lm Buflens: 56

But only the first two 'ptlrpc_body' and 'ldlm_reply' get decoded or even mentioned. I am guessing the thrid buffer is an ost_lvb, but I could well be wrong.
-Andrew

Issue Links

• is related to: LU-8499 wireshark plugins don't build any more
• is related to: LU-6353 Push Wireshark Support Upstream
• is related to: LU-6582 Wireshark fails to parse LDLM_ENQUEUE RPC - likely for layout lock
• is related to: LU-6648 Wireshark 1.8.10 does not correctly parse LDLM_ENQUEUE intent : getxattr
• is related to: LU-4931 New feature of giving server/storage side advice of accessing file
• is related to: LU-4378 Add HSM message parsing to wireshark plugins