From: Silas Boyd-Wickizer <sbw@mit.edu>
To: Rusty Russell <rusty@au1.ibm.com>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/4 V2] Use get_online_cpus to avoid races involving CPU hotplug
Date: Tue, 4 Sep 2012 09:36:09 -0700 [thread overview]
Message-ID: <20120904163608.GB14382@mit.edu> (raw)
In-Reply-To: <87k3whsalw.fsf@rustcorp.com.au>
Hi Rusty,
I used libsparse and kernel source annotations to check that code uses
for_each_online_cpu in contexts with hotplug disabled
(e.g. get_online_cpus(), preempt_disable, ..). I compiled with an x86
64-bit allyesconfig, so I missed other architecture specific usages.
The checker code isn't great and the results still require some manual
inspection for weeding out false positives, etc:
http://pdos.csail.mit.edu/~sbw/online-checker/
Silas
On Thu, Aug 30, 2012 at 06:02:11AM +0930, Rusty Russell wrote:
> Silas Boyd-Wickizer <sbw@mit.edu> writes:
>
> > Hello,
> >
> > This is the second version of the patches to fix races described in:
> >
> > https://groups.google.com/forum/?fromgroups#!topic/linux.kernel/iSUDr94Qehc
> >
> > The changes in this version are:
> >
> > * fix commit log typo;
> > * prevent a race in via_cputemp_exit;
> > * and a new patch that prevents races during init/exit in
> > drivers/hwmon/coretemp.c.
>
> Hi Silas,
>
> Good work! How did you find these?
>
> Cheers,
> Rusty.
>
prev parent reply other threads:[~2012-09-04 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 19:32 [PATCH 0/4 V2] Use get_online_cpus to avoid races involving CPU hotplug Silas Boyd-Wickizer
2012-08-29 20:32 ` Rusty Russell
2012-09-04 16:36 ` Silas Boyd-Wickizer [this message]
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=20120904163608.GB14382@mit.edu \
--to=sbw@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rusty@au1.ibm.com \
/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