linux-kernel - Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86

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]

Date:	Wed, 22 Nov 2006 15:25:59 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Kasper Sandberg <lkml@...anurb.dk>
Cc:	LKML Mailinglist <linux-kernel@...r.kernel.org>
Subject: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64

On Wed, 22 Nov 2006 15:29:02 +0100
Kasper Sandberg <lkml@...anurb.dk> wrote:

> it appears some sort of bug has gotten into .19, in regards to x86
> emulation on x86_64.
> 
> i have only tested with >=rc5, thw folling, as an example, appears in
> dmesg:
> ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02}
> arg(00221000) on /home/redeeman
> ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02}
> arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

	echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there.  Which kernel
version were you using previously (the one which didn't do this)?

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