[pnfs] wireshark patches
J. Bruce Fields
bfields at fieldses.org
Thu Nov 8 12:10:34 EST 2007
On Wed, Nov 07, 2007 at 10:27:30PM -0800, Dean Hildebrand wrote:
> Any clue which patch broke setclientid? (i.e., was it mine or was it
> already broken?) Not sure how my patches could have, but......you never
> know.
I don't know. From a quick skim through the patches.... Yes, I agree,
your patches don't seem mto touch anything 4.0-ish.
My bet would be on either the first patch--which seems to have some
changes that aren't related to 4.1 at all--or to some bug in upstream.
I probably won't get the chance to investigate any further soon, so if
someone else is interested, go for it. The current work is still at
git://linux-nfs.org/~bfields/wireshark.git
in the branch "master".
--b.
> More time for this after supercomputing....
>
> Dean
>
> J. Bruce Fields wrote:
>> I took the wireshark patches we had before, applied bakeathon patches I
>> got from Dean, rebased everything against the latest wireshark svn, and
>> built and tried it out. Unfortunately, it doesn't seem to parse nfsv4
>> setclientid calls or setclientid_confirm replies correctly.
>>
>> I won't have the time to deal with this any time soon; could someone
>> else take a look?
>>
>> I don't care if the new stuff (nfsv4.1/pnfs dissecting) is completely
>> right on the first attempt, but let's not break what's already there and
>> working....
>>
>> What I've got so far is here:
>>
>> git://linux-nfs.org/~bfields/wireshark.git
>>
>> --b.
>> _______________________________________________
>> pNFS mailing list
>> pNFS at linux-nfs.org
>> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>>
More information about the pNFS
mailing list