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

[Kasper Sandberg <lkml@metanurb.dk>]

On Wed, 2006-12-13 at 02:50 -0500, Chuck Ebbert wrote:
> In-Reply-To: <1165984783.23819.7.camel@localhost>
> 
> On Wed, 13 Dec 2006 05:39:43 +0100, Kasper Sandberg wrote:
> 
> > do you think it may be a bug in the kernel? the stuff with wine that
> > gets thrown in the kernel messages?
> 
> Let's just say the behavior has changed.  It now returns
> -EINVAL instead of -ENOTTY when the msdos IOCTLs fail.
> 
> > im 100% positive wine does NOT have
> > access to any fat32, cause i entirely removed the only disk having such
> > a filesystem, and it still likes to give this
> 
> That's when this happens: running certain programs that try
> msdos-type IOCTLs on native Linux filesystems.
ohhh :) well wine may do that :)
> 
> > however the last few
> > times i havent observed the app going nuts
> 
> If there aren't any other problems you can just turn off the logging.
> 
> Did you change something else?
i did upgrade from rc5 to final

> 
> Anyway, here is a much simpler patch that restores the previous
> behavior (but leaves the message.)  However if you aren't having
> any problems now other than the messages maybe there's no real
> problem after all?

well the hardlock problem still occurs, however that, (as i believe has
veen the semi-conclusion in this thread) arent related?

> 
> --- 2.6.19.1-64smp.orig/fs/compat.c
> +++ 2.6.19.1-64smp/fs/compat.c
> @@ -444,7 +444,11 @@ asmlinkage long compat_sys_ioctl(unsigne
>  
>  		if (++count <= 50)
>  			compat_ioctl_error(filp, fd, cmd, arg);
> -		error = -EINVAL;
> +
> +		if (cmd == 0x82187201)
> +			error = -ENOTTY;
> +		else
> +			error = -EINVAL;
>  	}
>  
>  	goto out_fput;