[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9af6b35d-bfbf-7f87-a419-042dff018fdd@oracle.com>
Date: Tue, 8 Oct 2019 11:13:23 -0700
From: Jane Chu <jane.chu@...cle.com>
To: n-horiguchi@...jp.nec.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/2] mm/memory-failure: Poison read receives SIGKILL
instead of SIGBUS issue
Hi, Naoya,
What is the status of the patches?
Is there anything I need to do from my end ?
Regards,
-jane
On 8/6/2019 10:25 AM, Jane Chu wrote:
> Change in v4:
> - remove trailing white space
>
> Changes in v3:
> - move **tk cleanup to its own patch
>
> Changes in v2:
> - move 'tk' allocations internal to add_to_kill(), suggested by Dan;
> - ran checkpatch.pl check, pointed out by Matthew;
> - Noaya pointed out that v1 would have missed the SIGKILL
> if "tk->addr == -EFAULT", since the code returns early.
> Incorporated Noaya's suggestion, also, skip VMAs where
> "tk->size_shift == 0" for zone device page, and deliver SIGBUS
> when "tk->size_shift != 0" so the payload is helpful;
> - added Suggested-by: Naoya Horiguchi <n-horiguchi@...jp.nec.com>
>
> Jane Chu (2):
> mm/memory-failure.c clean up around tk pre-allocation
> mm/memory-failure: Poison read receives SIGKILL instead of SIGBUS if
> mmaped more than once
>
> mm/memory-failure.c | 62 ++++++++++++++++++++++-------------------------------
> 1 file changed, 26 insertions(+), 36 deletions(-)
>
Powered by blists - more mailing lists