[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110610143550.GZ11521@ZenIV.linux.org.uk>
Date: Fri, 10 Jun 2011 15:35:50 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Eric Paris <eparis@...hat.com>
Cc: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: Race inotify_rm_watch vs umount
On Fri, Jun 10, 2011 at 09:46:05AM -0400, Eric Paris wrote:
> On Fri, 2011-06-10 at 20:20 +0900, OGAWA Hirofumi wrote:
> > Hi,
> >
> > I'm looking the race inotify_rm_watch() vs umount(). This race become the
> > cause of Oops. You can see the oops at
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=22602
> >
> > So, what race?
>
> Ok, I see what you are saying, I'll see what I can do. I'm a little
> scared to call something like iput() under a lock though. I might be
> able to make the bigest lock a mutex and fix this....
Which lock would that be? I don't see any good candidates in there...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists