public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Andi Kleen <ak@suse.de>
Cc: rmk@arm.linux.org.uk, torvalds@osdl.org, akpm@osdl.org,
	dwmw2@infradead.org, linux-arch@vger.kernel.org
Subject: Re: [patch 19/24] TASK_SIZE is variable.
Date: Sun, 6 Feb 2005 13:19:47 -0800	[thread overview]
Message-ID: <20050206131947.6524ece9.davem@davemloft.net> (raw)
In-Reply-To: <20050206105047.GB6819@wotan.suse.de>

On Sun, 6 Feb 2005 11:50:48 +0100
Andi Kleen <ak@suse.de> wrote:

> > First, "set_fs(KERNEL_DS)" allows kernel mode access, but it absolutely
> > must not allow user mode accesses.  It seems to suggest we might need
> > some "addr_min" value for access_ok() checking purposes...
> 
> That's an unreasonable requirement which no architecture other than
> those with truly separate address spaces follow.

If you allow userspace accesses to succeed during KERNEL_DS, so
much bad stuff can happen.  We've demonstrated that several times
with the compat layer bugs.

Why not make it trap on all platforms, instead of until someone hits
it on sparc64 or similar?

Do you like finding bugs immediately, or at some random time
in the future?  I like my bugs to jump up and down quickly
saying "I'm a bug" instead of "try and find me sucker" :-)

The x86 access_ok() already checks the address against a base
stored in the current_thread_info(), all I'm proposing is
to add a low value to the range as well and to adjust it at
set_fs() time, which set_fs() is already effectively doing on x86.

  reply	other threads:[~2005-02-06 21:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502050150.j151osl11380@mail.osdl.org>
2005-02-05  2:16 ` [patch 19/24] TASK_SIZE is variable Linus Torvalds
2005-02-05  3:29   ` Linus Torvalds
2005-02-05  5:52     ` David S. Miller
2005-02-07 10:59       ` David Howells
2005-02-07 19:30         ` David S. Miller
2005-02-08  9:05           ` Martin Schwidefsky
2005-02-08 19:09             ` David S. Miller
2005-02-05  9:06     ` Russell King
2005-02-05 23:44       ` David S. Miller
2005-02-06 10:50         ` Andi Kleen
2005-02-06 21:19           ` David S. Miller [this message]
2005-02-06 21:31             ` Andi Kleen
2005-02-06 21:31               ` David S. Miller
2005-02-06 21:50                 ` Andi Kleen
2005-02-06 22:25                   ` David S. Miller
2005-02-06 22:31                   ` David S. Miller
2005-02-07  8:11                     ` Andi Kleen
2005-02-07 19:28                       ` David S. Miller
2005-02-07 20:15                         ` Andi Kleen
2005-02-07 20:13                           ` David S. Miller
2005-02-05  6:54   ` Andi Kleen
2005-02-05  7:18     ` Andrew Morton
2005-02-05  7:40       ` Andi Kleen
2005-02-05 23:27         ` David S. Miller
2005-02-06 10:38           ` Andi Kleen
2005-02-06 13:05           ` Matthew Wilcox
2005-02-05 23:15       ` David S. Miller

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=20050206131947.6524ece9.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@osdl.org \
    /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