From: Andrew Morton <akpm@osdl.org>
To: schwidefsky@de.ibm.com
Cc: linux-arch@vger.kernel.org
Subject: Re: Fw: [PATCH] Fix zeroing on exception in copy_*_user
Date: Wed, 27 Sep 2006 09:18:30 -0700 [thread overview]
Message-ID: <20060927091830.a4c75810.akpm@osdl.org> (raw)
In-Reply-To: <1159349492.24891.16.camel@localhost>
On Wed, 27 Sep 2006 11:31:32 +0200
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> On Tue, 2006-09-26 at 17:11 -0700, Andrew Morton wrote:
> > I guess other architectures will need to do this. See
> > 01408c4939479ec46c15aa7ef6e2406be50eeeca and
> > 7c12d81134b130ccd4c286b434ca48c4cda71a2f for the rationale.
>
> Urgh, s390 does not have the problem that is does pad the leftover bytes
> in __copy_from_user_inatomic but that is does NOT pad the leftover bytes
> in __copy_from_user ..
>
That permits users to read uninitialised kernel memory by appending to a file
from a bad address then reading the result back....
next prev parent reply other threads:[~2006-09-27 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 0:11 Fw: [PATCH] Fix zeroing on exception in copy_*_user Andrew Morton
2006-09-27 9:31 ` Martin Schwidefsky
2006-09-27 16:18 ` Andrew Morton [this message]
2006-09-28 2:24 ` David 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=20060927091830.a4c75810.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.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