From: "Luck, Tony" <tony.luck@intel.com>
To: Brian Gerst <brgerst@gmail.com>, Andy Lutomirski <luto@amacapital.net>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Robert <elliott@hpe.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@ml01.01.org>
Subject: RE: [PATCH v8 1/3] x86: Expand exception table to allow new handling options
Date: Mon, 11 Jan 2016 23:48:12 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F39FAA697@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAMzpN2gamZbY+k=oADhAxEiNPEzeezaRDDOvF2ZU1rWG2CDNSA@mail.gmail.com>
> I agree that for at least put_user() using asm goto would be an even
> better option. get_user() on the other hand, will be much messier to
> deal with, since asm goto statements can't have outputs, plus it
> zeroes the output register on fault.
get_user() is the much more interesting one for me. A read from
a poisoned user address that generates a machine check is something
that can be recovered (kill the process). A write to user space doesn't
even generate a machine check.
-Tony
WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Brian Gerst <brgerst@gmail.com>, Andy Lutomirski <luto@amacapital.net>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Robert <elliott@hpe.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@ml01.01.org>
Subject: RE: [PATCH v8 1/3] x86: Expand exception table to allow new handling options
Date: Mon, 11 Jan 2016 23:48:12 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F39FAA697@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAMzpN2gamZbY+k=oADhAxEiNPEzeezaRDDOvF2ZU1rWG2CDNSA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 603 bytes --]
> I agree that for at least put_user() using asm goto would be an even
> better option. get_user() on the other hand, will be much messier to
> deal with, since asm goto statements can't have outputs, plus it
> zeroes the output register on fault.
get_user() is the much more interesting one for me. A read from
a poisoned user address that generates a machine check is something
that can be recovered (kill the process). A write to user space doesn't
even generate a machine check.
-Tony
N‹§²æìr¸›zǧu©ž²Æ {\b†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒðèž×¦j)Z†·Ÿ
next prev parent reply other threads:[~2016-01-11 23:48 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 0:04 [PATCH v8 0/3] Machine check recovery when kernel accesses poison Tony Luck
2016-01-09 0:04 ` Tony Luck
2015-12-31 19:40 ` [PATCH v8 2/3] x86, mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries Tony Luck
2015-12-31 19:40 ` Tony Luck
2016-01-08 20:49 ` [PATCH v8 1/3] x86: Expand exception table to allow new handling options Tony Luck
2016-01-08 20:49 ` Tony Luck
2016-01-09 1:52 ` Andy Lutomirski
2016-01-09 1:52 ` Andy Lutomirski
2016-01-09 3:39 ` Brian Gerst
2016-01-09 3:39 ` Brian Gerst
2016-01-09 4:31 ` Brian Gerst
2016-01-09 4:31 ` Brian Gerst
2016-01-09 6:36 ` Andy Lutomirski
2016-01-09 6:36 ` Andy Lutomirski
2016-01-11 23:09 ` Brian Gerst
2016-01-11 23:09 ` Brian Gerst
2016-01-11 23:22 ` Andy Lutomirski
2016-01-11 23:22 ` Andy Lutomirski
2016-01-11 23:48 ` Luck, Tony [this message]
2016-01-11 23:48 ` Luck, Tony
2016-01-09 17:45 ` Tony Luck
2016-01-09 17:45 ` Tony Luck
2016-01-09 18:00 ` Andy Lutomirski
2016-01-09 18:00 ` Andy Lutomirski
2016-01-09 19:51 ` Tony Luck
2016-01-09 19:51 ` Tony Luck
2016-01-09 22:32 ` Andy Lutomirski
2016-01-09 22:32 ` Andy Lutomirski
2016-01-10 1:15 ` Tony Luck
2016-01-10 1:15 ` Tony Luck
2016-01-11 0:25 ` Luck, Tony
2016-01-11 0:25 ` Luck, Tony
2016-01-08 21:18 ` [PATCH v8 3/3] x86, mce: Add __mcsafe_copy() Tony Luck
2016-01-08 21:18 ` Tony Luck
2016-01-09 1:49 ` Andy Lutomirski
2016-01-09 1:49 ` Andy Lutomirski
2016-01-09 17:48 ` Tony Luck
2016-01-09 17:48 ` Tony Luck
2016-01-09 17:57 ` Andy Lutomirski
2016-01-09 17:57 ` Andy Lutomirski
2016-01-09 19:39 ` Tony Luck
2016-01-09 19:39 ` Tony Luck
2016-01-09 22:15 ` Dan Williams
2016-01-09 22:15 ` Dan Williams
2016-01-09 22:33 ` Andy Lutomirski
2016-01-09 22:33 ` Andy Lutomirski
2016-01-10 0:23 ` Dan Williams
2016-01-10 0:23 ` Dan Williams
2016-01-10 1:40 ` Tony Luck
2016-01-10 1:40 ` Tony Luck
2016-01-10 11:26 ` Borislav Petkov
2016-01-10 11:26 ` Borislav Petkov
2016-01-11 10:44 ` Ingo Molnar
2016-01-11 10:44 ` Ingo Molnar
2016-01-13 23:22 ` Tony Luck
2016-01-13 23:22 ` Tony Luck
2016-01-14 4:39 ` Borislav Petkov
2016-01-14 4:39 ` Borislav Petkov
2016-01-30 0:35 ` Tony Luck
2016-01-30 0:35 ` Tony Luck
2016-01-30 10:28 ` Borislav Petkov
2016-01-30 10:28 ` Borislav Petkov
2016-02-01 23:10 ` Tony Luck
2016-02-01 23:10 ` Tony Luck
2016-02-01 23:16 ` Dan Williams
2016-02-01 23:16 ` Dan Williams
2016-01-12 0:26 ` Luck, Tony
2016-01-12 0:26 ` Luck, Tony
2016-01-12 0:30 ` Andy Lutomirski
2016-01-12 0:30 ` Andy Lutomirski
2016-01-12 0:37 ` Andy Lutomirski
2016-01-12 0:37 ` Andy Lutomirski
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=3908561D78D1C84285E8C5FCA982C28F39FAA697@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=x86@kernel.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.