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: <alpine.LFD.2.00.1002041150100.3707@localhost.localdomain>
Date:	Thu, 4 Feb 2010 11:54:55 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Sven Joachim <svenjoac@....de>
cc:	Greg KH <greg@...ah.com>, Ben Hutchings <ben@...adent.org.uk>,
	stable-review@...nel.org, stable@...nel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [stable] [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split



On Thu, 4 Feb 2010, Sven Joachim wrote:

> On 2010-02-04 20:11 +0100, Linus Torvalds wrote:
> 
> > Sven/Ben: is /sbin/init (or wherever debian puts it) a regular ELF file? 
> > Shared libraries? Anything at all special about it? I wonder why it seems 
> > to have issues, when other 32-bit programs don't.
> 
> ,----
> | % file /sbin/init
> | /sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
> | % ldd /sbin/init
> | 	linux-gate.so.1 =>  (0xf770d000)
> | 	libsepol.so.1 => /lib/libsepol.so.1 (0xf76c0000)
> | 	libselinux.so.1 => /lib/libselinux.so.1 (0xf76a6000)
> | 	libc.so.6 => /lib/i686/cmov/libc.so.6 (0xf755e000)
> | 	libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xf755a000)
> | 	/lib/ld-linux.so.2 (0xf770e000)
> `----
> 
> Apparently nothing special, and booting with init=/bin/bash does not
> change anything.

Yeah, well, if my current -git tree works, then there is something else 
going on. 

But I don't really see anything relevant _except_ for those commits. I do 
note that mainline also has the do_wait() thread optimizations since 
2.6.32, and I guess those aren't in stable, but I really don't see them 
interacting with that whole flush_old_exec thing in any way.

Very odd.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ