linux-kernel - Re: percpu related boot crash on x86 (was: Linux 2.6.38-rc1)

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: <20110119131329.GB14096@mtj.dyndns.org>
Date:	Wed, 19 Jan 2011 14:13:29 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: percpu related boot crash on x86 (was: Linux 2.6.38-rc1)

Hello,

On Wed, Jan 19, 2011 at 02:56:23PM +0200, Pekka Enberg wrote:
> Is vmalloc() and vfree() supposed to work with interrupts disabled? I
> always thought they weren't which would mean something in
> pcpu_mem_alloc() needs changing...

They aren't but percpu allocator doesn't call them with interrupts
disabled normally.  It only happens during early boot before it's
enabled for the first time but this is an allowed exception.  We'll
probably need to update the WARN_ON to consider the rare call path.
It also looks like something in that path is turning off/on IRQ
instead of saving/restoring it, so that probably needs to be changed
too but both aren't really critical.

I think the real problem is a lot of unsigned int percpu allocations
added by 6c9ae009 (irq: use per_cpu kstat_irqs).  percpu allocator
should be able to cope but it assumes that it would always be able to
allocate contiguous allocation map using vmalloc and that might be
failing, although I cannot readily see how or why that would happen
frequently on a 64bit machine.

Thanks.

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