[Cosmic][PATCH 0/1] fsnotify: Fix fsnotify_mark_connector race

[Joseph Salisbury]

On 05/23/2018 02:27 PM, Joseph Salisbury wrote:
> BugLink: http://bugs.launchpad.net/bugs/1771075
>
> == Cosmic Justification ==
> A regression was introduced by commit 08991e83b728.  This regression
> causes problems on hosts that make heavy use of inotify and causes panics / lockups 
> in the kernel in inotify-related code.
>
> This regression is fixed buy commit d90a10e2444b as of v4.17-rc3.  Commit d90a10e2444b
> was cc'd to stable and is already in Artful and Bionic but not Cosmic.
> The commit was added to A and B by bug 1765564.
>
> == Fix ==
> d90a10e2444b ("fsnotify: Fix fsnotify_mark_connector race")
>
> == Regression Potential ==
> Low.  Fixes a current regression. The patch was cc'd to stable, so it has had
> additional upstream review.  This commit is already applied to Artful
> and Bionic.
>
> == Test Case ==
> A test kernel was built with this patch and tested by the original bug reporter.
> The bug reporter states the test kernel resolved the bug.
>
> Robert Kolchmeyer (1):
>   fsnotify: Fix fsnotify_mark_connector race
>
>  include/linux/fsnotify_backend.h | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
This patch is also being requested in linux-gcp.  Should I send a v2, so
cosmic and linux-gcp are both listed in the subject?