[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHrFyr6rR=TMepEpFK0hQRQ-qMF8m4izf+WxdzGXEO7S_TVnQg@mail.gmail.com>
Date: Wed, 24 Apr 2019 18:19:25 +0200
From: Christian Brauner <christian@...uner.io>
To: Oleg Nesterov <oleg@...hat.com>
Cc: weizhenliang <weizhenliang@...wei.com>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"colona@...sta.com" <colona@...sta.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"arnd@...db.de" <arnd@...db.de>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"deepa.kernel@...il.com" <deepa.kernel@...il.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: Re: [PATCH v4] signal: trace_signal_deliver when signal_group_exit
On Wed, Apr 24, 2019 at 6:16 PM Oleg Nesterov <oleg@...hat.com> wrote:
>
> On 04/24, weizhenliang wrote:
> >
> > On 04/24, Oleg wrote:
> > >On 04/24, Christian Brauner wrote:
> > >>
> > >> On Wed, Apr 24, 2019 at 08:52:38PM +0800, Zhenliang Wei wrote:
> > >>
> > >> > Reviewed-by: Oleg Nesterov <oleg@...hat.com>
> > >
> > >Yes, but ...
> > >
> > >> > Reported-by: kbuild test robot <lkp@...el.com>
> > >
> > >Hmm, really?
> >
> > Yes, the kbuild test robot says that if I fix the problem with the third parameter type,
> > I should add this tag. What is wrong or missing?
>
> But this patch does not fix the problem reported by robot, your patch
> (which introduced that problem) was dropped, the problem has gone.
>
> With this "Reported-by: kbuild test robot <lkp@...el.com>" tag it looks
> as if test-robot has found the problem you are trying to fix: the lack of
> trace_signal_deliver(SIGKILL).
Yeah, Oleg's absolutely right. That tag should just go.
The Fixes line is all that we want, I think.
Christian
Powered by blists - more mailing lists