linux-kernel - Re: Large slowdown with 'x86: Avoid invoking RCU when CPU is idle'

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: <20120224144032.GA13903@zod.bos.redhat.com>
Date:	Fri, 24 Feb 2012 09:40:32 -0500
From:	Josh Boyer <jwboyer@...hat.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, kernel-team@...oraproject.org
Subject: Re: Large slowdown with 'x86: Avoid invoking RCU when CPU is idle'

On Tue, Feb 21, 2012 at 08:42:43PM -0500, Josh Boyer wrote:
> > And patch #47 in that series has been obsoleted by another series
> > from Steven Rostedt:
> > 
> > 	https://lkml.org/lkml/2012/2/7/231
> 
> Ok.
> 
> > Hopefully these fix both splats and slowness.
> 
> So again, I'm slightly confused on how RCU patches flow.  Eric
> originally reported the bug for which you created the patch I applied
> against 3.3.  The giant patch series above seems queued for 3.4.
> 
> I don't see stable CC'd on 45-47, nor any of Steven's patches.  I doubt
> I'd want to go applying the 47-patch series on 3.3 at the moment, and
> given you have these marked for 3.4 I don't think you do either.
> However, is there some kind of fix for the original bug report against
> 3.3?

I was being sincere when I asked the above questions.  Could you
describe how you handle RCU patches across releases and if there is a
fix for the 3.3-rcX issue Eric reported that is going into 3.3?

I know you're quite busy, but I'd like to understand your thinking so I
know what to expect going forward.

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