From: Ingo Molnar <mingo@elte.hu>
To: Robert Richter <robert.richter@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
oprofile-list <oprofile-list@lists.sourceforge.net>,
David Rientjes <rientjes@google.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/2] oprofile: fix race condition in event_buffer free
Date: Mon, 12 Oct 2009 23:28:11 +0200 [thread overview]
Message-ID: <20091012212811.GD4589@elte.hu> (raw)
In-Reply-To: <20091009195016.GH638@erda.amd.com>
* Robert Richter <robert.richter@amd.com> wrote:
> On 09.10.09 21:33:29, Robert Richter wrote:
> > From: David Rientjes <rientjes@google.com>
> >
> > Looking at the 2.6.31-rc9 code, it appears there is a race condition
> > in the event_buffer cleanup code path (shutdown). This could lead to
> > kernel panic as some CPUs may be operating on the event buffer AFTER
> > it has been freed. The attached patch solves the problem and makes
> > sure CPUs check if the buffer is not NULL before they access it as
> > some may have been spinning on the mutex while the buffer was being
> > freed.
> >
> > The race may happen if the buffer is freed during pending reads. But
> > it is not clear why there are races in add_event_entry() since all
> > workqueues or handlers are canceled or flushed before the event buffer
> > is freed.
> >
> > Signed-off-by: David Rientjes <rientjes@google.com>
> > Signed-off-by: Stephane Eranian <eranian@google.com>
> > Signed-off-by: Robert Richter <robert.richter@amd.com>
>
> Ingo,
>
> you can also pull the patches from here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
>
> Thanks.
Pulled, thanks Robert!
Ingo
next prev parent reply other threads:[~2009-10-12 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091009160532.GD638@erda.amd.com>
2009-10-09 19:33 ` [PATCH 1/2] oprofile: fix race condition in event_buffer free Robert Richter
2009-10-09 19:50 ` Robert Richter
2009-10-12 21:28 ` Ingo Molnar [this message]
2009-10-09 19:33 ` [PATCH 2/2] oprofile: warn on freeing event buffer too early Robert Richter
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=20091012212811.GD4589@elte.hu \
--to=mingo@elte.hu \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=rientjes@google.com \
--cc=robert.richter@amd.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;
as well as URLs for NNTP newsgroup(s).