Wireshark-bugs: [Wireshark-bugs] [Bug 13195] New: RPC/RDMA dissector should exit when frame is n
Date: Fri, 02 Dec 2016 19:34:07 +0000
Bug ID 13195
Summary RPC/RDMA dissector should exit when frame is not RPC-over-RDMA
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component TShark
Assignee bugzilla-admin@wireshark.org
Reporter chuck.lever@oracle.com

Created attachment 15098 [details]
Sample wire capture with improperly dissected RPC frame

Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-1601-gdfb1d07)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> 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.16, with Gcrypt 1.6.6, with MIT Kerberos, with GeoIP,
without nghttp2, without LZ4, without Snappy.

Running on Linux 4.8.10-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.16, with Gcrypt 1.6.6, with zlib
1.2.8.

Built using gcc 6.2.1 20160916 (Red Hat 6.2.1-2).
--
A sample wire capture is attached. Frame 385 is displayed as:

  385   0.086681      LID: 11 → LID: 5       RPC 226 V0 proc-0 Reply

This is not an RPC frame. It is being handed to the RPC dissector by the
RPC-over-RDMA dissector when that dissector doesn't recognize the frame
content.

However, RPC by itself cannot ever be present as an InfiniBand data payload. It
is either encapsulated by RPC-over-RDMA, or it is encapsulated by IPoIB and UDP
or TCP.


You are receiving this mail because:
  • You are watching all bug changes.