From: "David S. Miller" <davem@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
schwidefsky@de.ibm.com, arnd@arndb.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][COMPAT] compat_sys_fcntl{,64} 1/9 Generic part
Date: 12 Mar 2003 03:46:45 -0800 [thread overview]
Message-ID: <1047469604.15904.1.camel@rth.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0303112124000.12804-100000@home.transmeta.com>
On Tue, 2003-03-11 at 21:26, Linus Torvalds wrote:
> Yes, this looks much more sane. If you _really_ want to be anal about
> typechecking (and also checking that nobody can possibly use a user
> pointer incorrectly), you make
>
> typedef struct {
> unsigned int val;
> } compat_uptr_t;
Be careful, these kind of "int in a struct" things end up being
passed to functions on the stack instead of registers :-(
This is why we don't do any of the fancy type-checking
page table types on Sparc unless you edit the header files.
next prev parent reply other threads:[~2003-03-12 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 12:20 Martin Schwidefsky
2003-03-12 4:44 ` Stephen Rothwell
2003-03-12 5:02 ` Linus Torvalds
2003-03-12 5:22 ` Stephen Rothwell
2003-03-12 5:26 ` Linus Torvalds
2003-03-12 5:57 ` Stephen Rothwell
2003-03-12 11:46 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 0:41 Stephen Rothwell
2003-03-10 12:43 Arnd Bergmann
2003-03-04 5:58 Stephen Rothwell
2003-02-28 9:50 sfr
2003-02-28 10:36 ` Andi Kleen
2003-03-01 9:12 ` Anton Blanchard
2003-02-28 4:33 Stephen Rothwell
2003-02-28 8:08 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1047469604.15904.1.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®