| 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
| ||
|
Date: Tue, 24 Apr 2012 20:16:54 +0400 From: Michael Tokarev <mjt@....msk.ru> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: Ian Kent <raven@...maw.net>, "stable@...nel.org" <stable@...nel.org>, autofs@...r.kernel.org, Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Breaking userspace? Re: 3.0.24 broke aufofs on mixed 32/64bit environment On 24.04.2012 20:12, Michael Tokarev wrote: > On 24.04.2012 19:08, Linus Torvalds wrote: >>> Kernel has been shipping with this brokeness for quite >>> some time, namely, since introduction of autofs4, dated >>> Mon Mar 27 01:14:55 2006 -0800 (commit 5c0a32fc2cd0). >> >> Actually, that's just not true. The *main* users of the interface seem >> to have never fixed anything. As far as I know, neither the upstream >> autofs tools nor several of the big distributions ever had patches to >> make 32-bit autofs work with the old broken 64-bit compat layer. [] > I don't know how old this code is, but it definitely is in the > 5.0.1 upstream tarball, and the file there is dated > Feb-20, 2007 - at least 3 years after the initial bug in kernel. I meant to say "about a year after the initial bug in kernel". And I think it was me who found the original issue, -- i mean, discovered that it does not work, not found the real bug - but I don't remember anymore. This stuff looks very familiar for some reason however... ;) Thanks, /mjt -- 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