From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: bugme-daemon@bugzilla.kernel.org,
Yannick Dirou <yannick.dirou@axetic.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bug 10071] kernel hang in inet_init (PREEMPT_RCU problem)
Date: Thu, 28 Feb 2008 20:32:35 -0800 [thread overview]
Message-ID: <20080229043235.GA25167@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080229005823.GF14104@linux.vnet.ibm.com>
On Thu, Feb 28, 2008 at 04:58:23PM -0800, Paul E. McKenney wrote:
> On Thu, Feb 28, 2008 at 10:34:57PM +0100, Jarek Poplawski wrote:
> > On Thu, Feb 28, 2008 at 12:53:03PM -0800, bugme-daemon@bugzilla.kernel.org wrote:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10071
> > ...
> > > ------- Comment #17 from yannick.dirou@axetic.com 2008-02-28 12:53 -------
> > > bingo with classic rcu
> >
> > Congratulations Yannick!
> >
> > So, it seems mainly RCU vs. timer(?) problem. I send CC of this message
> > to RCU author, linux-kernel and netdev lists.
>
> Interesting! Any chance of a pointer to the original messages?
> A quick Google search and a look at LKML showed me nothing. :-/
Thanks to Raphael for pointing me at the above bugzilla URL!
Yannick,
Would you be willing to try your test again after applying the
patch in http://lkml.org/lkml/2008/2/2/11 and rebuilding your
kernel?
This patch does not appear to be in 2.6.25-rc3. :-(
I am reposting this patch separately.
Thanx, Paul
next prev parent reply other threads:[~2008-02-29 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10071-11547@http.bugzilla.kernel.org/>
[not found] ` <20080228205303.261D311D108@picon.linux-foundation.org>
2008-02-28 21:34 ` [Bug 10071] kernel hang in inet_init (PREEMPT_RCU problem) Jarek Poplawski
2008-02-29 0:58 ` Paul E. McKenney
2008-02-29 4:32 ` Paul E. McKenney [this message]
2008-02-29 6:53 ` Yannick
2008-02-29 16:58 ` Paul E. McKenney
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=20080229043235.GA25167@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yannick.dirou@axetic.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).