linux-kernel - Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549

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: <4B672059.3070405@zytor.com>
Date:	Mon, 01 Feb 2010 10:41:29 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jason Wessel <jason.wessel@...driver.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Simek <michal.simek@...alogix.com>,
	LKML <linux-kernel@...r.kernel.org>,
	John Williams <john.williams@...alogix.com>
Subject: Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549

On 02/01/2010 10:07 AM, Jason Wessel wrote:
> 
> Add to the afflicted architecture list a ppc64 kernel running 32 bit
> user space apps such as a dynamically linked busybox:
> 
> file bin/busybox
> 
> ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV),
> dynamically linked (uses shared libs), stripped
> 
> 
> All that is reported on boot is:
> 
> [clip]
> VFS: Mounted root (nfs filesystem) readonly on device 0:13.
> Freeing unused kernel memory: 264k freed
> /sbin/init: error while loading shared libraries: out of memory: Cannot
> allocate memory
> Kernel panic - not syncing: Attempted to kill init!
> Rebooting in 180 seconds..QEMU: Terminated
> 

That's is fully to be expected, since PowerPC also does the
TIF_ABI_PENDING garbage, which needs to be removed.

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