[quantal][sru] pull-request: fsnotify: simplify locking

[Tim Gardner]

On 12/29/2012 12:57 PM, Chris J Arges wrote:
> On 12/10/2012 12:05 PM, Chris J Arges wrote:
>> BugLink: http://bugs.launchpad.net/bugs/922906
>>
>> SRU Justification:
>>
>> Impact:
>> When plugging and unplugging a USB drive occasionally a race condition
>> in the notify subsystem causes a kernel oops. A more in depth explaining
>> can be found here: https://lkml.org/lkml/2011/1/19/213.
>>
>> Fix:
>> A set up of patches
>> 0520bffba9685d88ad68ede4a41abd08a3e9684e..fe9b25d3ee6bdf6f9c9a9ce61d9d3e144bac13ef
>> found in the for-next branch in the notify.git tree solve this issue:
>> http://git.infradead.org/users/eparis/notify.git/shortlog/refs/heads/for-next
>> These have been cherry-picked and tested on precise/quantal and applied
>> already to raring. Only small modifications are needed for 2 of the
>> patches because the locations of the functions had changed other than
>> that the other 7 patches are clean cherry-picks.
>>
> Note these patches have now been merged into mainline 3.8:
> https://lkml.org/lkml/2012/12/20/439
>
> I'm not sure if we need to reapply based on these commits or not. Let me
> know if any actions are needed as we've applied this to
> quantal/precise/raring already.
>
> Happy new year,
> --chris j arges
>
>
>

It appears that there is at least one more patch 
(6960b0d909cde5bdff49e4e5c1250edd10be7ebd) in the upstream series that 
addresses fsnotify locking. Would you care to review updates since v3.7 
and suggest a patch set to replace the SAUCE patches that we're carrying 
in Quantal master-next ?

rtg

-- 
Tim Gardner tim.gardner at canonical.com