| 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, 5 Dec 2006 21:31:42 -0500 From: Chuck Ebbert <76306.1226@...puserve.com> To: David Howells <dhowells@...hat.com> Cc: Andrew Morton <akpm@...l.org>, Kasper Sandberg <lkml@...anurb.dk>, linux-kernel <linux-kernel@...r.kernel.org>, ak@....de, vojtech@...e.cz Subject: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64 In-Reply-To: <26586.1165356671@...hat.com> On Tue, 05 Dec 2006 22:11:11 +0000, David Howells wrote: > > I only have 32-bit userspace. When I run your program against > > a directory on a JFS filesystem (msdos ioctls not supported) > > I get this on vanilla 2.6.19: > > Can I just check? You're using an x86_64 CPU in 64-bit mode with a 64-bit > kernel, but with a completely 32-bit userspace? It's FC5 i386 so there's no way any 64-bit userspace code is in there. (I have a cross-compiler only for building kernels.) Having a pure 32-bit userspace lets me switch between i386 and x86_64 kernels without having to maintain two separate Linux installs. > A question for you: Why is userspace assuming that it'll get ENOTTY rather > than EINVAL? I'm not sure it is, but that's what it used to get. Kasper, what problems (other that the annoying message) are you having? -- Chuck "Even supernovas have their duller moments." - 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