diff options
| author | Jan Kara <jack@suse.cz> | 2017-10-31 12:09:25 +0300 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2017-10-31 19:54:56 +0300 |
| commit | 9cf90cef362d44b2f3fcdb7d0694849a6308b620 (patch) | |
| tree | 7eac90d6bf1a97b485d6a3b7483042089d3756d7 /include/linux/fsnotify_backend.h | |
| parent | b3a0066005821acdc0cdb092cb72587182ab583f (diff) | |
| download | linux-9cf90cef362d44b2f3fcdb7d0694849a6308b620.tar.xz | |
fsnotify: Protect bail out path of fsnotify_add_mark_locked() properly
When fsnotify_add_mark_locked() fails it cleans up the mark it was
adding. Since the mark is already visible in group's list, we should
protect update of mark->flags with mark->lock. I'm not aware of any real
issues this could cause (since we also hold group->mark_mutex) but
better be safe and obey locking rules properly.
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'include/linux/fsnotify_backend.h')
0 files changed, 0 insertions, 0 deletions