Wireshark-bugs: [Wireshark-bugs] [Bug 4839] The NFS FH hash (nfs.fh.hash) incorrectly matches mu
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 3 Jun 2010 16:08:50 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4839

--- Comment #2 from Cal Turney <turney_cal@xxxxxxx> 2010-06-03 16:08:49 PDT ---
Created an attachment (id=4756)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4756)
Capture that demonstrates the problem and the fix. 

Steps to reproduce the overlapping FH hash problem

1. Open capture Overlapping_FH_hash.cap

2. Go to frame 63, right-click on "filehandle", select 
   'Apply as filter' -> Selected, click Apply.  WS displays 25 frames.

3. On frame 60, right-click on 'hash', click Apply as filter -> Selected.
   Now 61 frames are displayed.  Filter "nfs.fh.hash == 0x0218ae55" incorrectly
   matches multiple NFS filehandles.

4. After the patch is applied, do step #3 again which will produce
   'nfs.fh.hash == 0xdd81ca48' and apply it.
   27 frames are displayed. The extra 2 frames, 59 and 62 match the filter
   due to the presence of the pseudo hash fields that WS includes in those
  frames (which is a nice feature).

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.