public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] rcu classic: new algorithm for callbacks-processing
Date: Fri, 1 Aug 2008 14:09:29 -0700	[thread overview]
Message-ID: <20080801210929.GF14851@linux.vnet.ibm.com> (raw)
In-Reply-To: <48708F23.2080702@cn.fujitsu.com>

On Sun, Jul 06, 2008 at 05:23:47PM +0800, Lai Jiangshan wrote:
> Paul E. McKenney wrote:
> 
> > 
> > You tried this without your changes and it passed, correct?
> > 
> > Never forget to test the base kernel.  ;-)
> > 
> 
> Thanks, but I make some mistake here.
> 
> I tested the base kernel, no bug occurred.
> So I try to find out bugs in my changes in 2 weeks.
> 
> I added debug codes and these codes showed all processing
> are right and no callback broke its grace period
> but the bug still occurred.
> 
> When I was puzzled after 2 weeks, I looked back the base
> kernel that I had tested, and I found that I forget to set
> CONFIG_NO_HZ=y.
> 
> Then I set CONFIG_NO_HZ=y in the base kernel, and the bug
> occurred. It's exactly as the bug when my patch applied.
> 
> I have reported this bug here:
> http://lkml.org/lkml/2008/7/3/24

Hello, Jiangshan,

Does Gautham's patch (http://lkml.org/lkml/2008/6/27/9) help?

							Thanx, Paul

      reply	other threads:[~2008-08-01 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  3:46 [RFC][PATCH] rcu classic: new algorithm for callbacks-processing Lai Jiangshan
2008-06-08 15:18 ` Paul E. McKenney
2008-06-23  3:25   ` Lai Jiangshan
2008-06-23  9:13     ` Paul E. McKenney
2008-07-06  9:23       ` Lai Jiangshan
2008-08-01 21:09         ` Paul E. McKenney [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=20080801210929.GF14851@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --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