| Bug ID |
13261
|
| Summary |
packet-rpcrdma: properly dissect RDMA_NOMSG messages
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-1823-gef92e9f)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.48.2, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, without
Lua, with GnuTLS 3.4.17, with Gcrypt 1.6.6, with MIT Kerberos, with GeoIP,
without nghttp2, without LZ4, without Snappy.
Running on Linux 4.8.14-200.fc24.x86_64, with Intel(R) Core(TM) i7-5557U CPU @
3.10GHz (with SSE4.2), with 1981 MB of physical memory, with locale
en_US.UTF-8,
with libpcap version 1.7.4, with GnuTLS 3.4.17, with Gcrypt 1.6.6, with zlib
1.2.8.
Built using gcc 6.2.1 20160916 (Red Hat 6.2.1-2).
--
An RPC-over-RDMA message may move a whole RPC Call or Reply using an RDMA Read
or Write. In this case the RPC message itself is not forwarded to any
subdissectors, and appears as an RPCoRDMA protocol frame of type RDMA_NOMSG.
The RPC-over-RDMA dissector should use the chunk lists in that frame to find
the associated RDMA Read or Write requests and re-assemble them into a full RPC
message, then pass that on to an appropriate subdissector.
You are receiving this mail because:
- You are watching all bug changes.