linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: Wetp Zhang <wetp.zy@linux.alibaba.com>
Cc: n-horiguchi@ah.jp.nec.com, naoya.horiguchi@nec.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] mm, memory_failure: don't send BUS_MCEERR_AO for action required error
Date: Sat, 30 May 2020 09:08:43 +0200	[thread overview]
Message-ID: <CAM9Jb+jWnAPUYpJ-QrUR1oBCj+RwdAZMLyO4GCmAq=8V76VQTw@mail.gmail.com> (raw)
In-Reply-To: <1590817116-21281-1-git-send-email-wetp.zy@linux.alibaba.com>

> Some processes dont't want to be killed early, but in "Action Required"
> case, those also may be killed by BUS_MCEERR_AO when sharing memory
> with other which is accessing the fail memory.
> And sending SIGBUS with BUS_MCEERR_AO for action required error is
> strange, so ignore the non-current processes here.
>
> Suggested-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> Signed-off-by: Wetp Zhang <wetp.zy@linux.alibaba.com>
> ---
>  mm/memory-failure.c | 15 +++++++++------
>  1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index a96364be8ab4..dd3862fcf2e9 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -210,14 +210,17 @@ static int kill_proc(struct to_kill *tk, unsigned long pfn, int flags)
>  {
>         struct task_struct *t = tk->tsk;
>         short addr_lsb = tk->size_shift;
> -       int ret;
> +       int ret = 0;
>
> -       pr_err("Memory failure: %#lx: Sending SIGBUS to %s:%d due to hardware memory corruption\n",
> -               pfn, t->comm, t->pid);
> +       if ((t->mm == current->mm) || !(flags & MF_ACTION_REQUIRED))
> +               pr_err("Memory failure: %#lx: Sending SIGBUS to %s:%d due to hardware memory corruption\n",
> +                       pfn, t->comm, t->pid);

Maybe we can generalize the message condition for better readability.
Thought a bit but did not get any other idea.
>
> -       if ((flags & MF_ACTION_REQUIRED) && t->mm == current->mm) {
> -               ret = force_sig_mceerr(BUS_MCEERR_AR, (void __user *)tk->addr,
> -                                      addr_lsb);
> +       if (flags & MF_ACTION_REQUIRED) {
> +               if (t->mm == current->mm)
> +                       ret = force_sig_mceerr(BUS_MCEERR_AR,
> +                                        (void __user *)tk->addr, addr_lsb);
> +               /* send no signal to non-current processes */
>         } else {
>                 /*
>                  * Don't use force here, it's convenient if the signal
> --

Looks good to me.
Acked-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>

  reply	other threads:[~2020-05-30  7:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30  5:38 [PATCH V2] mm, memory_failure: don't send BUS_MCEERR_AO for action required error Wetp Zhang
2020-05-30  7:08 ` Pankaj Gupta [this message]
2020-06-01  3:11   ` HORIGUCHI NAOYA(堀口 直也)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM9Jb+jWnAPUYpJ-QrUR1oBCj+RwdAZMLyO4GCmAq=8V76VQTw@mail.gmail.com' \
    --to=pankaj.gupta.linux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=wetp.zy@linux.alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).