[Ocfs2-devel] dentry locks

[Sunil Mushran <Sunil.Mushran@oracle.com>]

Mark Fasheh wrote:
> Yeah, it breaks the protocol  ;)

I meant, other than that. As in, we can always queue up this change
the next time we break the protocol for a better reason.


> What do the tcp dumps look like? Is it raw binary data, is the binary
> converted into hex, etc?

dentry lock from debugfs: N0000000000000005000d6a02
raw tcpdump: 4e303030303030303030303030303030350000000000000d6a02

N 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 00          0d6a02
4e303030303030303030303030303030350000000000000d6a02

As all other locknames are strings, if I need to wade thru tcpdumps,
I simply grep. If not for that, one can easily spend a day just searching
for the appropriate packets. So this is not a useless exercise.