summaryrefslogtreecommitdiffstats
path: root/fs/bfs/bfs.h
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2018-02-21 14:10:59 +0100
committerJan Kara <jack@suse.cz>2018-02-27 10:25:33 +0100
commit1f5eaa90010ed7cf0ae90a526c48657d02c6086f (patch)
treeaccb9faea9a7b5160d5e35f320007938e2f76af9 /fs/bfs/bfs.h
parentf0c4a81711cb773b60cb8f90173e6491e67bf74f (diff)
downloadlinux-1f5eaa90010ed7cf0ae90a526c48657d02c6086f.tar.bz2
fanotify: Avoid lost events due to ENOMEM for unlimited queues
Fanotify queues of unlimited length do not expect events can be lost. Since these queues are used for system auditing and other security related tasks, loosing events can even have security implications. Currently, since the allocation is small (32-bytes), it cannot fail however when we start accounting events in memcgs, allocation can start failing. So avoid loosing events due to failure to allocate memory by making event allocation use __GFP_NOFAIL. Reviewed-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/bfs/bfs.h')
0 files changed, 0 insertions, 0 deletions