From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: wetp <wetp.zy@linux.alibaba.com>
Cc: "n-horiguchi@ah.jp.nec.com" <n-horiguchi@ah.jp.nec.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm, memory_failure: only send BUS_MCEERR_AO to early-kill process
Date: Fri, 29 May 2020 06:43:53 +0000 [thread overview]
Message-ID: <20200529064353.GA14362@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <e4da056c-8d6c-9687-0785-b1900cb7c3e2@linux.alibaba.com>
On Fri, May 29, 2020 at 01:56:25PM +0800, wetp wrote:
> On 2020/5/29 上午10:12, HORIGUCHI NAOYA(堀口 直也) wrote:
...
> > > > > @@ -225,8 +225,9 @@ static int kill_proc(struct to_kill *tk, unsigned long pfn, int flags)
> > > > > * This could cause a loop when the user sets SIGBUS
> > > > > * to SIG_IGN, but hopefully no one will do that?
> > > > > */
> > > > > - ret = send_sig_mceerr(BUS_MCEERR_AO, (void __user *)tk->addr,
> > > > > - addr_lsb, t); /* synchronous? */
> > > > > + if ((t->flags & PF_MCE_PROCESS) && (t->flags & PF_MCE_EARLY))
> > > > > + ret = send_sig_mceerr(BUS_MCEERR_AO,
> > > > > + (void __user *)tk->addr, addr_lsb, t);
> > > > kill_proc() could be called only for processes that are selected by
> > > > collect_procs() with task_early_kill(). So I think that we should fix
> > > > task_early_kill(), maybe by reordering sysctl_memory_failure_early_kill
> > > > check and find_early_kill_thread() check.
> > > >
> > > > static struct task_struct *task_early_kill(struct task_struct *tsk,
> > > > int force_early)
> > > > {
> > > > struct task_struct *t;
> > > > if (!tsk->mm)
> > > > return NULL;
> > > > if (force_early)
> > > > return tsk;
> > > The force_early is rely the flag MF_ACTION_REQUIRED, so it is always true
> > > when MCE occurs.
> > >
> > > This leads always sending SIGBUS to processes even if those are not current
> > > or no flag setting.
> > >
> > > I think it could keep the non-current processes which has no flag setting
> > > running.
> > >
> > >
> > > Besides, base on your recommendation I reorder the force_early check and
> > > find_early_kill_thread()
> > >
> > > check, to send the signal to the right thread.
> > Sorry, my previous comment around task_early_kill() is for a separate problem,
> > so I'll try some fix on this later.
> Thanks.
>
> Should me send the patch V2 for my problem alone? Or you will fix it with
> task_early_kill() together ?
You can send v2 if you like. Please note that patch description should be
descriptive enough for future reference.
I'm working on related testing now. I guess that action optional cases are
not tested well enough from current process context because there's no useful
injector.
Thanks,
Naoya Horiguchi
prev parent reply other threads:[~2020-05-29 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 7:06 Wetp Zhang
2020-05-28 2:22 ` HORIGUCHI NAOYA(堀口 直也)
2020-05-28 6:50 ` wetp
2020-05-29 2:12 ` HORIGUCHI NAOYA(堀口 直也)
2020-05-29 5:56 ` wetp
2020-05-29 6:43 ` 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=20200529064353.GA14362@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=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