linux-kernel - Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Nov 2015 11:16:11 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
	linux-edac@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover
 from machine checks


* Luck, Tony <tony.luck@...el.com> wrote:

> On Thu, Nov 12, 2015 at 08:53:13AM +0100, Ingo Molnar wrote:
> > > +extern phys_addr_t mcsafe_memcpy(void *dst, const void __user *src,
> > > +				unsigned size);
> > 
> > So what's the longer term purpose, where will mcsafe_memcpy() be used?
> 
> The initial plan is to use this for file systems backed by NVDIMMs. They will 
> have a large amount of memory, and we have a practical recovery path - return 
> -EIO just like legacy h/w.
> 
> We can look for other places in the kernel where we read large amounts of memory 
> and have some idea how to recover if the memory turns out to be bad.

I see, that's sensible!

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/