All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>,
	Al Viro <viro@math.psu.edu>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Finding user/kernel pointer bugs [no html]
Date: Thu, 10 Jun 2004 11:26:39 -0400	[thread overview]
Message-ID: <40C87DAF.902@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406100754270.2050@ppc970.osdl.org>



Linus Torvalds wrote:

>>If you really want to force user space accesses to follow certain rules, 
>>make them longs or structs (or at least void *) (depending on 
>>architecture) so that only the proper user-space-access functions can 
>>interpret them.
> 
> 
> .. and this would be a total disaster.
> 
> Think about it. The user pointer isn't just a "value". It has a type it 
> points to. We want to do


Makes sense.  Too many things my short-sighted suggestion didn't account 
for.



  reply	other threads:[~2004-06-10 15:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  3:31 Finding user/kernel pointer bugs [no html] Robert T. Johnson
2004-06-10  4:10 ` Linus Torvalds
2004-06-10  4:48   ` Robert T. Johnson
2004-06-10 14:46     ` Linus Torvalds
2004-06-10 16:57       ` viro
2004-06-10 15:07   ` Timothy Miller
2004-06-10 15:04     ` Linus Torvalds
2004-06-10 15:26       ` Timothy Miller [this message]
2004-06-10  4:49 ` viro
2004-06-10  5:20   ` Robert T. Johnson
2004-06-10 16:58   ` Greg KH
2004-06-10 17:27     ` David Brownell
2004-06-10 17:35       ` Greg KH
2004-06-10 17:54     ` Thomas Sailer
2004-06-10 18:34     ` Greg KH
2004-06-10 18:45       ` viro
2004-06-10 18:54         ` Greg KH
2004-06-10 19:10     ` Greg KH
2005-05-19  6:25       ` Greg KH
2004-06-10 19:14       ` viro
2005-05-19  6:25         ` viro
2004-06-10 19:32         ` Greg KH
2005-05-19  6:25           ` Greg KH
2004-06-10 19:38           ` viro
2005-05-19  6:25             ` viro
2004-06-10 20:28           ` Sam Ravnborg
2005-05-19  6:25             ` Sam Ravnborg
2004-06-10 20:48             ` Randy.Dunlap
2005-05-19  6:25               ` Randy.Dunlap
2004-06-11 17:21       ` Jean Delvare
2005-05-19  6:25         ` Jean Delvare
2004-06-11 17:59         ` Greg KH
2005-05-19  6:25           ` Greg KH

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=40C87DAF.902@techsource.com \
    --to=miller@techsource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtjohnso@eecs.berkeley.edu \
    --cc=torvalds@osdl.org \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.