linux-kernel - Re: [PATCH] efibc: avoid stack overflow warning

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: <2137916.p0oDBh93bk@wuerfel>
Date:	Sun, 01 May 2016 01:25:12 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Matt Fleming <matt@...eblueprint.co.uk>
Cc:	"Compostella, Jeremy" <jeremy.compostella@...el.com>,
	Ingo Molnar <mingo@...nel.org>, linux-efi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] efibc: avoid stack overflow warning

On Saturday 30 April 2016 23:46:41 Matt Fleming wrote:
> 
> > It's not something we'd have to worry about in practice, but it does
> > make my patch incorrect. Should we come up with a different way to
> > do it?
> 
> Jeremy proposed a patch to dynamically allocate the memory, which I
> think is the correct way to go given that our (reasonable) assumptions
> about reboot notifier concurrency are not guaranteed,
> 
>   https://lkml.kernel.org/r/87h9eked24.fsf@jcompost-MOBL1.tl.intel.com

Sure, that works. I considered doing it that way but it seemed more
complicated. Please use that patch instead of mine.

	Arnd