From: kmcmarti@redhat.com (Kyle McMartin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: __clear_user: handle exceptions on strb
Date: Thu, 13 Nov 2014 10:14:08 -0500 [thread overview]
Message-ID: <20141113151407.GG6869@redacted.bos.redhat.com> (raw)
In-Reply-To: <20141113150624.GB18494@e104818-lin.cambridge.arm.com>
On Thu, Nov 13, 2014 at 03:06:25PM +0000, Catalin Marinas wrote:
> On Wed, Nov 12, 2014 at 09:07:44PM +0000, Kyle McMartin wrote:
> > ARM64 currently doesn't fix up faults on the single-byte (strb) case of
> > __clear_user... which means that we can cause a nasty kernel panic as an
> > ordinary user with any multiple PAGE_SIZE+1 read from /dev/zero.
> > i.e.: dd if=/dev/zero of=foo ibs=1 count=1 (or ibs=65537, etc.)
>
> Thanks for this, it's been like this for a while. Applied.
>
Thanks Catalin, if it's not too late, I forgot to add a
Reported-by: Milo? Prchl?k <mprchlik@redhat.com>
for the initial report of the panic.
regards, Kyle
WARNING: multiple messages have this Message-ID (diff)
From: Kyle McMartin <kmcmarti@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pmatouse@redhat.com" <pmatouse@redhat.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: __clear_user: handle exceptions on strb
Date: Thu, 13 Nov 2014 10:14:08 -0500 [thread overview]
Message-ID: <20141113151407.GG6869@redacted.bos.redhat.com> (raw)
In-Reply-To: <20141113150624.GB18494@e104818-lin.cambridge.arm.com>
On Thu, Nov 13, 2014 at 03:06:25PM +0000, Catalin Marinas wrote:
> On Wed, Nov 12, 2014 at 09:07:44PM +0000, Kyle McMartin wrote:
> > ARM64 currently doesn't fix up faults on the single-byte (strb) case of
> > __clear_user... which means that we can cause a nasty kernel panic as an
> > ordinary user with any multiple PAGE_SIZE+1 read from /dev/zero.
> > i.e.: dd if=/dev/zero of=foo ibs=1 count=1 (or ibs=65537, etc.)
>
> Thanks for this, it's been like this for a while. Applied.
>
Thanks Catalin, if it's not too late, I forgot to add a
Reported-by: Miloš Prchlík <mprchlik@redhat.com>
for the initial report of the panic.
regards, Kyle
next prev parent reply other threads:[~2014-11-13 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 21:07 [PATCH] arm64: __clear_user: handle exceptions on strb Kyle McMartin
2014-11-12 21:07 ` Kyle McMartin
2014-11-13 15:06 ` Catalin Marinas
2014-11-13 15:06 ` Catalin Marinas
2014-11-13 15:14 ` Kyle McMartin [this message]
2014-11-13 15:14 ` Kyle McMartin
2014-11-13 15:21 ` Catalin Marinas
2014-11-13 15:21 ` Catalin Marinas
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=20141113151407.GG6869@redacted.bos.redhat.com \
--to=kmcmarti@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 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.