aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
diff options
context:
space:
mode:
authorAmir Goldstein <[email protected]>2020-07-16 08:42:27 +0000
committerJan Kara <[email protected]>2020-07-27 21:24:00 +0000
commit5128063739d293b9faf8ffaa9a5dfd622bc954f5 (patch)
treed1ef6993402d190ad3f7339d17fb050e0c52906d /drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
parentfanotify: add basic support for FAN_REPORT_DIR_FID (diff)
downloadkernel-5128063739d293b9faf8ffaa9a5dfd622bc954f5.tar.gz
kernel-5128063739d293b9faf8ffaa9a5dfd622bc954f5.zip
fanotify: report events with parent dir fid to sb/mount/non-dir marks
In a group with flag FAN_REPORT_DIR_FID, when adding an inode mark with FAN_EVENT_ON_CHILD, events on non-directory children are reported with the fid of the parent. When adding a filesystem or mount mark or mark on a non-dir inode, we want to report events that are "possible on child" (e.g. open/close) also with fid of the parent, as if the victim inode's parent is interested in events "on child". Some events, currently only FAN_MOVE_SELF, should be reported to a sb/mount/non-dir mark with parent fid even though they are not reported to a watching parent. To get the desired behavior we set the flag FAN_EVENT_ON_CHILD on all the sb/mount/non-dir mark masks in a group with FAN_REPORT_DIR_FID. Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Amir Goldstein <[email protected]> Signed-off-by: Jan Kara <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c')
0 files changed, 0 insertions, 0 deletions