From: Huang Ying <ying.huang@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATH -mm -v2] Fix a race condtion of oops_in_progress
Date: Wed, 29 Oct 2008 16:42:16 +0800 [thread overview]
Message-ID: <1225269736.24095.50.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20081029083434.GC6364@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Wed, 2008-10-29 at 02:34 -0600, Ingo Molnar wrote:
> * Huang Ying <ying.huang@intel.com> wrote:
>
> > Fix a race condition accessing oops_in_progress. Which may be
> > changed on multiple CPU simultaneously, but it is changed via
> > non-atomic operation ++/--. This patch changes the definition of
> > oops_in_process from int to atomic_t, and accessing method to atomic
> > operations.
> >
> >
> > ChangeLog
> >
> > v2:
> >
> > - Includes fixes from Andrew Moton.
> >
> > - Re-based on Matthew Wilcox's new atomic_t patch.
>
> hm, there are a couple of places now that do atomic_set(,1) - they
> should be atomic_inc(), correct?
I just translate "oops_in_progress = 1" to
"atomic_set(&oops_in_progress, 1)". I think this is the safest method to
do the translation.
Best Regards,
Huang Ying
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-29 8:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 8:26 Huang Ying
2008-10-29 8:34 ` Ingo Molnar
2008-10-29 8:42 ` Huang Ying [this message]
2008-10-29 14:51 ` Chris Snook
2008-10-30 2:02 ` Huang Ying
2008-10-31 16:42 ` Chris Snook
2008-11-03 1:52 ` Huang Ying
2008-11-03 18:44 ` Chris Snook
2008-11-04 1:41 ` Huang Ying
2008-11-10 7:35 ` KOSAKI Motohiro
2008-11-10 18:45 ` Chris Snook
2008-11-11 1:05 ` Huang Ying
2008-11-11 1:10 ` Chris Snook
2008-11-11 1:19 ` Huang Ying
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=1225269736.24095.50.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome