fsnotify cleanups
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | fsnotify: Document mark lockinginclude/ | +30 | 0 replies | |
| 2/3 | fsnotify: Remove mark->free_listfs/ fs/ fs/ +3 more | +40 | 0 replies | |
| 3/3 | fsnotify: Get rid of fsnotify_destroy_mark_locked()fs/ fs/ fs/ +1 more | +61 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] fsnotify cleanups
Hello,
after understanding some of the fsnotify mark handling code when fixing
the last race I've decided to use that knowledge to improve the documentation and somewhat cleanup the code.
The first patch in the series documents locking rules for fsnotify marks. The second patch gets rid of special purpose free_list list head in the fsnotify mark structure and the third patch splits the fsnotify_destroy_mark_locked() function so that it doesn't have the awkward property of temporarily dropping mark_mutex which can cause unexpected issues in the caller.
All the patches have survived beating with LTP inotify and fanotify tests (including the test excercising inode & group destruction races).
Honza