Centos-kernel-stream-10/fs/notify
Ian Kent 0bafcea5fd fsnotify: fix sending inotify event with unexpected filename
JIRA: https://issues.redhat.com/browse/RHEL-68847
Upstream status: Linux

commit aa52c54da40d9eee3ba87c05cdcb0cd07c04fa13
Author: Amir Goldstein <amir73il@gmail.com>
Date:   Wed Nov 13 16:40:34 2024 +0100

    fsnotify: fix sending inotify event with unexpected filename

    We got a report that adding a fanotify filsystem watch prevents tail -f
    from receiving events.

    Reproducer:

    1. Create 3 windows / login sessions. Become root in each session.
    2. Choose a mounted filesystem that is pretty quiet; I picked /boot.
    3. In the first window, run: fsnotifywait -S -m /boot
    4. In the second window, run: echo data >> /boot/foo
    5. In the third window, run: tail -f /boot/foo
    6. Go back to the second window and run: echo more data >> /boot/foo
    7. Observe that the tail command doesn't show the new data.
    8. In the first window, hit control-C to interrupt fsnotifywait.
    9. In the second window, run: echo still more data >> /boot/foo
    10. Observe that the tail command in the third window has now printed
    the missing data.

    When stracing tail, we observed that when fanotify filesystem mark is
    set, tail does get the inotify event, but the event is receieved with
    the filename:

    read(4, "\1\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0foo\0\0\0\0\0\0\0\0\0\0\0\0\0",
    50) = 32

    This is unexpected, because tail is watching the file itself and not its
    parent and is inconsistent with the inotify event received by tail when
    fanotify filesystem mark is not set:

    read(4, "\1\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0", 50) = 16

    The inteference between different fsnotify groups was caused by the fact
    that the mark on the sb requires the filename, so the filename is passed
    to fsnotify().  Later on, fsnotify_handle_event() tries to take care of
    not passing the filename to groups (such as inotify) that are interested
    in the filename only when the parent is watching.

    But the logic was incorrect for the case that no group is watching the
    parent, some groups are watching the sb and some watching the inode.

    Reported-by: Miklos Szeredi <miklos@szeredi.hu>
    Fixes: 7372e79c9e ("fanotify: fix logic of reporting name info with watched parent")
    Cc: stable@vger.kernel.org # 5.10+
    Signed-off-by: Amir Goldstein <amir73il@gmail.com>
    Signed-off-by: Jan Kara <jack@suse.cz>

Signed-off-by: Ian Kent <ikent@redhat.com>
2024-11-28 12:54:42 +08:00
..
dnotify inotify: Fix possible deadlock in fsnotify_destroy_mark 2024-10-02 15:14:29 +02:00
fanotify inotify: Fix possible deadlock in fsnotify_destroy_mark 2024-10-02 15:14:29 +02:00
inotify fsnotify: Avoid data race between fsnotify_recalc_mask() and fsnotify_object_watched() 2024-10-02 15:11:40 +02:00
Kconfig
Makefile
fdinfo.c fsnotify: Avoid -Wflex-array-member-not-at-end warning 2024-03-26 10:53:32 +01:00
fdinfo.h
fsnotify.c fsnotify: fix sending inotify event with unexpected filename 2024-11-28 12:54:42 +08:00
fsnotify.h fsnotify: clear PARENT_WATCHED flags lazily 2024-06-05 09:52:38 +02:00
group.c inotify: Fix possible deadlock in fsnotify_destroy_mark 2024-10-02 15:14:29 +02:00
mark.c fsnotify: Avoid data race between fsnotify_recalc_mask() and fsnotify_object_watched() 2024-10-02 15:11:40 +02:00
notification.c