From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Cc: Wetp Zhang <wetp.zy@linux.alibaba.com>,
"n-horiguchi@ah.jp.nec.com" <n-horiguchi@ah.jp.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: Mon, 1 Jun 2020 03:11:25 +0000 [thread overview]
Message-ID: <20200601031124.GA5418@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <CAM9Jb+jWnAPUYpJ-QrUR1oBCj+RwdAZMLyO4GCmAq=8V76VQTw@mail.gmail.com>
On Sat, May 30, 2020 at 09:08:43AM +0200, Pankaj Gupta wrote:
> > 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.
This odd condition might imply that we could have better fix in
task_early_kill(), but that should come after fixing priority issue of
early-kill flag, so let's go with this fix for now.
> >
> > - 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>
Thanks!
Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
prev parent reply other threads:[~2020-06-01 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 5:38 Wetp Zhang
2020-05-30 7:08 ` Pankaj Gupta
2020-06-01 3:11 ` HORIGUCHI NAOYA(堀口 直也) [this message]
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=20200601031124.GA5418@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.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=pankaj.gupta.linux@gmail.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