diff options
| author |   Gabriel Krisman Bertazi <krisman@collabora.com> | 2021-10-25 16:27:28 -0300 |
|---|---|---|
| committer |   Jan Kara <jack@suse.cz> | 2021-10-27 12:34:25 +0200 |
| commit | 12f47bf0f0990933d95d021d13d31bda010648fd (patch) | |
| tree | 91e6308596227c968bf9452aa737c79e3bcddeda /fs/notify | |
| parent | fsnotify: Pass group argument to free_event (diff) | |
| download | linux-dev-12f47bf0f0990933d95d021d13d31bda010648fd.tar.xz linux-dev-12f47bf0f0990933d95d021d13d31bda010648fd.zip | |
fanotify: Support null inode event in fanotify_dfid_inode
FAN_FS_ERROR doesn't support DFID, but this function is still called for
every event. The problem is that it is not capable of handling null
inodes, which now can happen in case of superblock error events. For
this case, just returning dir will be enough.
Link: https://lore.kernel.org/r/20211025192746.66445-14-krisman@collabora.com
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/notify')
| -rw-r--r-- | fs/notify/fanotify/fanotify.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c index c620b4f6fe12..397ee623ff1e 100644 --- a/fs/notify/fanotify/fanotify.c +++ b/fs/notify/fanotify/fanotify.c @@ -452,7 +452,7 @@ static struct inode *fanotify_dfid_inode(u32 event_mask, const void *data, if (event_mask & ALL_FSNOTIFY_DIRENT_EVENTS) return dir; - if (S_ISDIR(inode->i_mode)) + if (inode && S_ISDIR(inode->i_mode)) return inode; return dir; |