linux-kernel - Re: [block IO crash] Re: 2.6.39-rc5-git2 boot crashs

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:	Wed, 4 May 2011 19:12:20 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Christoph Lameter <cl@...ux.com>, Tejun Heo <tj@...nel.org>,
	Pekka Enberg <penberg@...nel.org>,
	Jens Axboe <axboe@...nel.dk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	werner <w.landgraf@...ru>, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [block IO crash] Re: 2.6.39-rc5-git2 boot crashs

On Wed, 4 May 2011, Ingo Molnar wrote:

> 
> * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> > My gut reaction would be: let's do the minimal patch that just fixes things 
> > to do irqsafe_cpu_cmpxchg_double() for 2.6.39, and then let's remove the 
> > #ifdef'fery in -rc1. [...]
> 
> Looks like the sanest option IMHO, -rc7 is pretty late for anything than a 
> few-liner patch.

Agreed.
 
> > [...] Or make _really_ sure that things are ok for platforms that never even 
> > triggered the CMPXCHG_LOCAL case before.
> 
> Considering that the status quo was !CMPXCHG_LOCAL in v2.6.38 and that lockless 
> SLUB is an x86-only affair right now:
> 
>  $ git grep CMPXCHG_LOCAL arch/
>  arch/um/Kconfig.x86:config CMPXCHG_LOCAL
>  arch/x86/Kconfig.cpu:config CMPXCHG_LOCAL
> 
> There should be no problem with other architectures, right?

No, they use the local_irq disabled path which is pretty much the same
as in 38.

Thanks,

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