On Wed, Jun 29, 2005 at 04:41:27PM +1000, Stephen Rothwell wrote: > On Tue, 28 Jun 2005 13:47:36 -0700 (PDT) "David S. Miller" <[EMAIL > PROTECTED]> wrote: > > > > Why don't we do the following to resolve this issue? > > Create a "is_compat_syscall()" macro, in compat syscall > > trap entry, the bit is set, and it is cleared otherwise. > > > > It nops out to always evaluate to "0" on non-compat platforms. > > How about the patch below which defines is_compat_syscall() for ppc64 (and > all the non-compat-requiring archs)? (Yes, the ppc64 syscall entry really > checks the thread flag.) The patch alos includes the fixes for the input > layer mess. > for the other 64 bit architectures.
I think for the particular input case it would be still better to just define ->compat_write at the VFS level. This would require a new compat_sys_write() wrapper, but that would be straight forward. -Andi
