On Wed, May 01, 2024 at 05:24:56PM -0600, Jane Chu wrote: > For years when it comes down to kill a process due to hwpoison, > a SIGBUS is delivered only if unmap has been successful. > Otherwise, a SIGKILL is delivered. And the reason for that is > to prevent the involved process from accessing the hwpoisoned > page again. > > Since then a lot has changed, a hwpoisoned page is marked and > upon being re-accessed, the process will be killed immediately. > So let's take out the '!unmap_success' factor and try to deliver > SIGBUS if possible. I am missing some details here. An unmapped hwpoison page will trigger a fault and will return VM_FAULT_HWPOISON all the way down and then deliver SIGBUS, but if the page was not unmapped, how will this be catch upon re-accessing? Will the system deliver a MCE event? -- Oscar Salvador SUSE Labs
