Re: [PATCH] Start of compat32.h (again)

David Mosberger (davidm@napali.hpl.hp.com)
Wed, 27 Nov 2002 09:10:47 -0800


>>>>> On Wed, 27 Nov 2002 01:57:17 -0800 (PST), "David S. Miller" <davem@redhat.com> said:

DaveM> You need to have a different kernel exit path, you need a
DaveM> different one to chop off the top 32-bits of all the incoming
DaveM> arguments anyways David.

You conveniently cut of the important part of my message:

Remember that most compatibility syscalls go straight to the
64-bit syscall handlers. You're probably hosed anyhow if a
64-bit syscall returns, say, 0x1ffffffff, but on ia64 I'd
still rather play it safe and consistently have all
compatibility syscalls return a 64-bit sign-extended value
like all other syscall handlers ("least surprise" principle).

I have zero interest debugging subtle bugs of this sort. If "long"
isn't an option, we should add a platform-specific compat32_retval_t
or whatever.

--david
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/