Re: [PATCH] fanotify: fix race between fanotify_release() and fanotify_get_response()

On Wed 24-08-16 11:55:39, Miklos Szeredi wrote: > List corruption was reported with a fanotify stress test. > > The bug turned out to be due to fsnotify_remove_event() being called on an > event on the fanotify_data.access_list and protected by > fanotify_data.access_lock instead of

Re: [PATCH] fanotify: fix race between fanotify_release() and fanotify_get_response()

On Wed 24-08-16 11:55:39, Miklos Szeredi wrote: > List corruption was reported with a fanotify stress test. > > The bug turned out to be due to fsnotify_remove_event() being called on an > event on the fanotify_data.access_list and protected by > fanotify_data.access_lock instead of

[PATCH] fanotify: fix race between fanotify_release() and fanotify_get_response()

List corruption was reported with a fanotify stress test. The bug turned out to be due to fsnotify_remove_event() being called on an event on the fanotify_data.access_list and protected by fanotify_data.access_lock instead of notification_mutex. This resulted in list_del_init() being run

[PATCH] fanotify: fix race between fanotify_release() and fanotify_get_response()

List corruption was reported with a fanotify stress test. The bug turned out to be due to fsnotify_remove_event() being called on an event on the fanotify_data.access_list and protected by fanotify_data.access_lock instead of notification_mutex. This resulted in list_del_init() being run