From: Mark Rutland <mark.rutland@arm.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-arm-kerne@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>,
Laura Abbott <labbott@redhat.com>,
Russell King <linux@armlinux.org.uk>,
stable <stable@vger.kernel.org>,
steve.capper@arm.com, Will Deacon <will.deacon@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/2] Fatal signal handing within uaccess faults
Date: Tue, 11 Jul 2017 16:10:53 +0100 [thread overview]
Message-ID: <20170711151053.GG2681@leverpostej> (raw)
In-Reply-To: <CALCETrX_T5=9Y77Z7VrM+YcpoFiJkhUGFNTOh2KbuG+7cey-bw@mail.gmail.com>
On Tue, Jul 11, 2017 at 08:04:50AM -0700, Andy Lutomirski wrote:
> On Tue, Jul 11, 2017 at 7:16 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> > Hi,
> >
> > Arch maintainer tl;dr: most arch fault code doesn't handle fatal signals
> > correctly, allowing unprivileged users to create an unkillable task which can
> > lock up the system. Please check whether your arch is affected.
>
> I haven't tested for real, but brief inspection of the code suggests
> that x86 is okay.
AFAICT, yes.
As mentioned later on in the message, I beleive it's been ok since
commit:
26178ec11ef3c6c8 ("x86: mm: consolidate VM_FAULT_RETRY handling")
... and my test-case didn't trigger anything in local testing on my
desktop.
Mark.
next prev parent reply other threads:[~2017-07-11 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 14:16 [PATCH 0/2] Fatal signal handing within uaccess faults Mark Rutland
2017-07-11 14:16 ` [PATCH 1/2] arm64: mm: abort uaccess retries upon fatal signal Mark Rutland
2017-07-11 14:16 ` [PATCH 2/2] arm: " Mark Rutland
2017-07-11 14:18 ` [PATCH 0/2] Fatal signal handing within uaccess faults Mark Rutland
2017-07-11 15:04 ` Andy Lutomirski
2017-07-11 15:10 ` Mark Rutland [this message]
2017-08-22 10:25 ` Mark Rutland
2017-08-22 10:25 ` Mark Rutland
2017-08-22 10:25 ` Mark Rutland
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 14:19 Mark Rutland
2017-07-11 14:19 ` Mark Rutland
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=20170711151053.GG2681@leverpostej \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=labbott@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kerne@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=steve.capper@arm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.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 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.