From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] more vfs.git stuff
Date: Thu, 9 May 2013 21:28:15 +0100 [thread overview]
Message-ID: <20130509202815.GH25399@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFyCuksrVPwO=R_xX2An8qavo17aCZ5bfN=FWo1gZZfAsQ@mail.gmail.com>
On Thu, May 09, 2013 at 01:12:43PM -0700, Linus Torvalds wrote:
> On Thu, May 9, 2013 at 12:26 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > Regression fix from Geert + yet another open-coded kernel_read().
>
> Hmm. I get one more commit - a racy usbmon thing.
Oops - pull stats not updated... My apologies.
> Which looks fine per
> se, but would look even better if it just made mmap_active an atomic_t
> instead, wouldn't you say?
The only place checking that sucker is in a fairly large area protected by
->b_lock (in mon_bin_event()); I really don't want to dig deep enough to
tell if having it changed right after it had been checked is safe. OTOH,
from a cursory look through that code it appears that the whole map_count
thing is completely misguided - it seems to assume that ->open() is called for
each VMA, including the one created by mmap(2). Sigh...
OK, it might make more sense to drop that last commit for now. It's obviously
more broken in mmap-related code than just a buggered locking for counter
and it probably doesn't make much sense to patch just that one. And I'll
have several more fixes of similar turds tomorrow, when mchehab finishes
testing videobuf ones. Up to you, really.
next prev parent reply other threads:[~2013-05-09 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 19:26 [git pull] more vfs.git stuff Al Viro
2013-05-09 20:12 ` Linus Torvalds
2013-05-09 20:21 ` Linus Torvalds
2013-05-09 20:28 ` Al Viro [this message]
2013-05-09 20:34 ` Al Viro
2013-05-09 20:46 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2016-01-21 23:04 Al Viro
2016-01-22 18:26 ` Linus Torvalds
2016-01-22 18:42 ` Al Viro
2016-01-22 18:45 ` Linus Torvalds
2013-07-14 17:34 Al Viro
2013-05-07 19:17 Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130509202815.GH25399@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).