From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] fix for nasty races in br_write_lock()
Date: Thu, 22 Dec 2011 07:09:12 +0000 [thread overview]
Message-ID: <20111222070912.GL23916@ZenIV.linux.org.uk> (raw)
There's a nasty race between CPU hotplug and br_write_lock();
the latter pretty much assumes that the set of online CPUs can't change
between br_write_lock() and br_write_unlock(). Caught by Cong Meng,
solution hashed out during the last few days between me and Srivatsa S. Bhat
on l-k/fsdevel thread, appears to fix the problem in a reasonably sane
way. It'll need to go into -stable as well; all branches since 2.6.36.
Please, pull from the usual place;
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Srivatsa S. Bhat (1):
VFS: Fix race between CPU hotplug and lglocks
Diffstat:
include/linux/lglock.h | 36 ++++++++++++++++++++++++++++++++----
1 files changed, 32 insertions(+), 4 deletions(-)
reply other threads:[~2011-12-22 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111222070912.GL23916@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).