From: Andy Lutomirski <luto@amacapital.net>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Ingo Molnar" <mingo@kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Snitzer" <snitzer@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"X86 ML" <x86@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Mika Penttilä" <mika.penttila@nextfour.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Christoph Hellwig" <hch@lst.de>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: use memcpy_mcsafe() for copy_to_iter() (was: Re: [PATCH v3 0/9] Series short description)
Date: Mon, 14 May 2018 10:53:51 -0700 [thread overview]
Message-ID: <3CEE65FC-2314-4837-9854-80E73ECBF0EE@amacapital.net> (raw)
In-Reply-To: <CAPcyv4j2HQH1wdsGGWUAiXEKXeoMUWN_HeUEMmkv8PG7RUTtfw@mail.gmail.com>
> On May 14, 2018, at 8:52 AM, Dan Williams <dan.j.williams@intel.com> wrote:
>
>
> I think "happy" is a strong word when it comes to x86 machine check
> handling. My interpretation is that he and Andy acquiesced that this
> is about the best we can do with dax+mce as things stand today.
Agreed. I think it’s plausible that we could do slightly better for MCEs related to bad memory accessed through the direct map, but the code would be complicated and miserable to test, and it’s not even clear that it would materially decrease the chance that we survive as compared to these patches.
next prev parent reply other threads:[~2018-05-14 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 17:10 use memcpy_mcsafe() for copy_to_iter() (was: Re: [PATCH v3 0/9] Series short description) Dan Williams
2018-05-14 7:26 ` Ingo Molnar
2018-05-14 15:52 ` Dan Williams
2018-05-14 17:53 ` Andy Lutomirski [this message]
2018-05-14 19:20 ` Linus Torvalds
2018-05-15 6:49 ` Ingo Molnar
2018-05-15 17:20 ` Dan Williams
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=3CEE65FC-2314-4837-9854-80E73ECBF0EE@amacapital.net \
--to=luto@amacapital.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mika.penttila@nextfour.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=snitzer@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).