linux-kernel - Re: [RFC][PATCH] rcu classic: new algorithm for callbacks-processing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48708F23.2080702@cn.fujitsu.com>
Date:	Sun, 06 Jul 2008 17:23:47 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] rcu classic: new algorithm for callbacks-processing

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/