RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults

(off-list ancestor, not in this archive)
[PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Tony Luck <tony.luck@intel.com> · 2022-10-19
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Dan Williams <hidden> · 2022-10-19
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · "Luck, Tony" <tony.luck@intel.com> · 2022-10-19
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-20
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Tony Luck <tony.luck@intel.com> · 2022-10-20
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Miaohe Lin <linmiaohe@huawei.com> · 2022-10-21
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · "Luck, Tony" <tony.luck@intel.com> · 2022-10-21
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-21
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Tony Luck <tony.luck@intel.com> · 2022-10-21
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · David Laight <hidden> · 2022-10-21
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · "Luck, Tony" <tony.luck@intel.com> · 2022-10-21
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-21
RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · "Luck, Tony" <tony.luck@intel.com> · 2022-10-21
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-23
Re: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-21
[PATCH v3 0/2] Copy-on-write poison recovery · Tony Luck <tony.luck@intel.com> · 2022-10-21
[PATCH v3 2/2] mm, hwpoison: When copy-on-write hits poison, take page offline · Tony Luck <tony.luck@intel.com> · 2022-10-21
Re: [PATCH v3 2/2] mm, hwpoison: When copy-on-write hits poison, take page offline · Miaohe Lin <linmiaohe@huawei.com> · 2022-10-28
RE: [PATCH v3 2/2] mm, hwpoison: When copy-on-write hits poison, take page offline · "Luck, Tony" <tony.luck@intel.com> · 2022-10-28
Re: [PATCH v3 2/2] mm, hwpoison: When copy-on-write hits poison, take page offline · Miaohe Lin <linmiaohe@huawei.com> · 2022-10-29
[PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · Tony Luck <tony.luck@intel.com> · 2022-10-21
Re: [PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · HORIGUCHI NAOYA (堀口　直也) <hidden> · 2022-10-25
Re: [PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · Miaohe Lin <linmiaohe@huawei.com> · 2022-10-28
RE: [PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · "Luck, Tony" <tony.luck@intel.com> · 2022-10-28
Re: [PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · Alexander Potapenko <glider@google.com> · 2022-11-02
Re: [PATCH v3 1/2] mm, hwpoison: Try to recover from copy-on write faults · Alexander Potapenko <glider@google.com> · 2022-11-02
Re: [PATCH v3 0/2] Copy-on-write poison recovery · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-23
Re: [PATCH v3 0/2] Copy-on-write poison recovery · Shuai Xue <xueshuai@linux.alibaba.com> · 2022-10-26
[PATCH v4 0/2] Copy-on-write poison recovery · Tony Luck <tony.luck@intel.com> · 2022-10-31
[PATCH v4 1/2] mm, hwpoison: Try to recover from copy-on write faults · Tony Luck <tony.luck@intel.com> · 2022-10-31
[PATCH v4 2/2] mm, hwpoison: When copy-on-write hits poison, take page offline · Tony Luck <tony.luck@intel.com> · 2022-10-31

From: David Laight <hidden>
Date: 2022-10-21 04:11:33
Also in: linux-mm, lkml

From: Tony Luck

Sent: 21 October 2022 05:08

....

When we do return to user mode the task is going to be busy servicing
a SIGBUS ... so shouldn't try to touch the poison page before the
memory_failure() called by the worker thread cleans things up.

What about an RT process on a busy system?
The worker threads are pretty low priority.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help