[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5d9412b0de4410084b4b8d111784b13@intel.com>
Date: Wed, 8 Sep 2021 17:01:39 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>
CC: "x86@...nel.org" <x86@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexei Starovoitov <ast@...nel.org>,
Peter Ziljstra <peterz@...radead.org>,
Song Liu <songliubraving@...com>,
Daniel Borkmann <daniel@...earbox.net>
Subject: RE: [patch V3 00/20] x86/fpu: Clean up exception fixups and error
handling in sigframe related code
> Much better. This version boots. Machine check recovery works as well as it did before
> (user triggered machine checks are fine, kernel triggered ones are ok where they were
> before and still trigger infinite loops where they did before).
With these three patches:
https://lore.kernel.org/all/20210818002942.1607544-1-tony.luck@intel.com/
on top of your series the infinite loops are fixed (first patch).
Other two patches fix my write(2) test which does:
ret = write(fd, buf, 512);
Where I have injected poison at some offset within "buf".
If the poison is at the start of buf I get ret == -1 with errno == -EFAULT.
If the poison is at a non-zero offset, the the bytes up to the poison
are written to the file and "ret" tells you how many were written.
-Tony
Powered by blists - more mailing lists