On Tue, 05 Dec 2006 03:36:09 +0100 Kasper Sandberg <[EMAIL PROTECTED]> wrote:
> i know i said i suspected this was another bug, but i have revised my > suspecisions, and i do believe its in relation to x86 chroot on x86_64 > install, as it has happened with more stuff now, inside the chroot, and > only inside the chroot, while the same apps dont do it outside chroot. > > 2.6.19 release is affected too Please don't top-post. > On Wed, 2006-11-22 at 15:25 -0800, Andrew Morton wrote: > > On Wed, 22 Nov 2006 15:29:02 +0100 > > Kasper Sandberg <[EMAIL PROTECTED]> 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)? Possibly some ioctl got removed. I don't know why it would only occur within a chrooted environment. Possibly one could work out what's going on by reverse-engineering x86_64 ioctl command 0x82187201, but unfortunately I don't have time to do that. Also unfortunately there appears to be an assumption that unless I personally can immediately and straightforwardly identify a bug-owner, I personally own the bug. The best I can suggest is that you raise a report at bugzilla.kernel.org so this issue gets ignored in a more organised fashion. Sorry. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/