[Bugs] [Bug 1534602] New: FUSE reverse notificatons are not written to fuse dump

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1534602

            Bug ID: 1534602
           Summary: FUSE reverse notificatons are not written to fuse dump
           Product: GlusterFS
           Version: mainline
         Component: fuse
          Assignee: bugs at gluster.org
          Reporter: csaba at redhat.com
                CC: bugs at gluster.org



Description of problem:

With the --dump-fuse option, the glusterfs fuse client writes out fuse traffic
to the given dump file. Reverese messages (aka. notifications) that are
initiated by the glusterfs client (FUSE server) are not recorded in the dump.

Version-Release number of selected component (if applicable):

All.

How reproducible:

Always.

Steps to Reproduce:
1. Mount a gluster volume with direct glusterfs invocation, using --dump-fuse:

# glusterfs --volfile-server=<host> --volfile-id=<vol>
--dump-fuse=/path/to/dump.fuse ... <mountpoint>

2. On some file of the gluster mount, trigger an entry invalidation with

$ setfattr -n inode-invalidate -v whatever <file>

(the "whatever" can be whatever, just not an empty string!)

3. Compile parsefuse (https://github.com/csabahenk/parsefuse/, at this commit:
https://github.com/csabahenk/parsefuse/commit/0232410 or later) for the
glusterfs setup used, and feed it with the fuse dump and seek NOTIFY in the
output:

$ sudo cat /path/to/dump.fuse | parsefuse | grep NOTIFY

Actual results:

Nada.

Expected results:

Entry shown with NOTIFY_INVAL_ENTRY label.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.