linux-kernel - Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced

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]

Date:	Fri, 20 Jul 2012 11:36:19 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>,
	mgalbraith@...ell.com, mmokrejs@...d.natur.cuni.cz
Subject: Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced

On Fri, Jul 20, 2012 at 04:24:25PM +0800, Michael Wang wrote:
> On 07/20/2012 02:41 PM, Dan Carpenter wrote:
> > My bug was fixed in March.  There was an email thread about it when
> > the merge window opened but I can't find it...
> Hi, Dan
> 
> Thanks for your reply.
> 
> Currently this issue won't appear because the
> CONFIG_RCU_CPU_STALL_TIMEOUT=60, which is big enough to avoid the
> warning info.
> 
> So is this the fix you mentioned? or someone has find out the true
> reason and fixed it?

I don't think there was an email thread on the RCU stall issue after
all.  I'm not sure what how it was fixed.

The 60 second time out would have still triggered with my bug.  It
was a complete system hang, the RCU stall message was just a
debugging hint.  I was hitting the bug every couple days reliably on
all my systems.

regards,
dan carpenter

--
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/