Re: WARNING in task_participate_group_stop (2)

On 04/29, syzbot wrote: > > RIP: 0010:task_participate_group_stop+0x205/0x260 kernel/signal.c:351 > RSP: 0018:8801ae7b7880 EFLAGS: 00010093 > RAX: 8801d96200c0 RBX: RCX: 81498b5b > RDX: RSI: 81498c75 RDI: 0005 > RBP:

Re: WARNING in task_participate_group_stop (2)

On 04/29, syzbot wrote: > > RIP: 0010:task_participate_group_stop+0x205/0x260 kernel/signal.c:351 > RSP: 0018:8801ae7b7880 EFLAGS: 00010093 > RAX: 8801d96200c0 RBX: RCX: 81498b5b > RDX: RSI: 81498c75 RDI: 0005 > RBP:

WARNING in task_participate_group_stop (2)

Hello, syzbot hit the following crash on upstream commit bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +) MAINTAINERS: add myself as maintainer of AFFS syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=b109633ea805cac54a61 So far this crash happened 2

WARNING in task_participate_group_stop (2)

Hello, syzbot hit the following crash on upstream commit bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +) MAINTAINERS: add myself as maintainer of AFFS syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=b109633ea805cac54a61 So far this crash happened 2

Re: WARNING in task_participate_group_stop

On Mon, Nov 6, 2017 at 3:31 PM, Oleg Nesterov wrote: > On 11/06, Jamie Iles wrote: >> >> I'm unable to reproduce the warning in qemu with SMP (on a 32 CPU VM). > > Neither me. Perhaps because I tried this test-case on the minimal system > with /bin/sh running as init process. >

Re: WARNING in task_participate_group_stop

On Mon, Nov 6, 2017 at 3:31 PM, Oleg Nesterov wrote: > On 11/06, Jamie Iles wrote: >> >> I'm unable to reproduce the warning in qemu with SMP (on a 32 CPU VM). > > Neither me. Perhaps because I tried this test-case on the minimal system > with /bin/sh running as init process. > >> Instead I get

Re: WARNING in task_participate_group_stop

On 11/06, Jamie Iles wrote: > > I'm unable to reproduce the warning in qemu with SMP (on a 32 CPU VM). Neither me. Perhaps because I tried this test-case on the minimal system with /bin/sh running as init process. > Instead I get the following instant traceback which is different to what > you

Re: WARNING in task_participate_group_stop

On 11/06, Jamie Iles wrote: > > I'm unable to reproduce the warning in qemu with SMP (on a 32 CPU VM). Neither me. Perhaps because I tried this test-case on the minimal system with /bin/sh running as init process. > Instead I get the following instant traceback which is different to what > you

Re: WARNING in task_participate_group_stop

On Mon, Nov 06, 2017 at 12:56:09PM +0100, Dmitry Vyukov wrote: > On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote: > > Hi Dmitry, > > > > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: > >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov

Re: WARNING in task_participate_group_stop

On Mon, Nov 06, 2017 at 12:56:09PM +0100, Dmitry Vyukov wrote: > On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote: > > Hi Dmitry, > > > > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: > >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: > >> > On 11/01, Dmitry Vyukov

Re: WARNING in task_participate_group_stop

On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote: > Hi Dmitry, > > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: >> > On 11/01, Dmitry Vyukov wrote: >> >> >> >> On Tue, Oct 31, 2017

Re: WARNING in task_participate_group_stop

On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote: > Hi Dmitry, > > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: >> > On 11/01, Dmitry Vyukov wrote: >> >> >> >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: >> >>

Re: WARNING in task_participate_group_stop

Hi Dmitry, On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: > On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: > > On 11/01, Dmitry Vyukov wrote: > >> > >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > >> > Hmm. I do not see

Re: WARNING in task_participate_group_stop

Hi Dmitry, On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote: > On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: > > On 11/01, Dmitry Vyukov wrote: > >> > >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > >> > Hmm. I do not see reproducer in this email... > >> > >> Ah,

Re: WARNING in task_participate_group_stop

On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: > On 11/01, Dmitry Vyukov wrote: >> >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: >> > Hmm. I do not see reproducer in this email... >> >> Ah, sorry. You can see full thread with attachments here:

Re: WARNING in task_participate_group_stop

On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote: > On 11/01, Dmitry Vyukov wrote: >> >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: >> > Hmm. I do not see reproducer in this email... >> >> Ah, sorry. You can see full thread with attachments here: >>

Re: WARNING in task_participate_group_stop

On 11/01, Dmitry Vyukov wrote: > > On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > > Hmm. I do not see reproducer in this email... > > Ah, sorry. You can see full thread with attachments here: > https://groups.google.com/forum/#!topic/syzkaller-bugs/EUmYZU4m5gU Heh. I

Re: WARNING in task_participate_group_stop

On 11/01, Dmitry Vyukov wrote: > > On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > > Hmm. I do not see reproducer in this email... > > Ah, sorry. You can see full thread with attachments here: > https://groups.google.com/forum/#!topic/syzkaller-bugs/EUmYZU4m5gU Heh. I can't say I enjoyed

Re: WARNING in task_participate_group_stop

On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > On 10/30, Dmitry Vyukov wrote: >> >> On Mon, Oct 30, 2017 at 10:12 PM, syzbot >> >> wrote: >> > Hello, >> > >> > syzkaller hit the following crash on

Re: WARNING in task_participate_group_stop

On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote: > On 10/30, Dmitry Vyukov wrote: >> >> On Mon, Oct 30, 2017 at 10:12 PM, syzbot >> >> wrote: >> > Hello, >> > >> > syzkaller hit the following crash on >> > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 >> >

Re: WARNING in task_participate_group_stop

On 10/30, Dmitry Vyukov wrote: > > On Mon, Oct 30, 2017 at 10:12 PM, syzbot > > wrote: > > Hello, > > > > syzkaller hit the following crash on > > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 > >

Re: WARNING in task_participate_group_stop

On 10/30, Dmitry Vyukov wrote: > > On Mon, Oct 30, 2017 at 10:12 PM, syzbot > > wrote: > > Hello, > > > > syzkaller hit the following crash on > > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 > > git://git.cmpxchg.org/linux-mmots.git/master > > compiler: gcc (GCC) 7.1.1 20170620 > > .config is

Re: WARNING in task_participate_group_stop

On Mon, Oct 30, 2017 at 10:12 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620

Re: WARNING in task_participate_group_stop

On Mon, Oct 30, 2017 at 10:12 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > C reproducer

[PATCH 0/1] (Was: WARNING in task_participate_group_stop)

On 11/02, Oleg Nesterov wrote: > > and I think this should be fixed anyway, if nothing else to make this logic > more > correct. Yes, please see the patch. > I'll try to recheck this all later. I found more problems, will try to send the fixes/cleanups tomorrow... do_signal_stop() is buggy, a

[PATCH 0/1] (Was: WARNING in task_participate_group_stop)

On 11/02, Oleg Nesterov wrote: > > and I think this should be fixed anyway, if nothing else to make this logic > more > correct. Yes, please see the patch. > I'll try to recheck this all later. I found more problems, will try to send the fixes/cleanups tomorrow... do_signal_stop() is buggy, a

Re: WARNING in task_participate_group_stop

On 11/02, Oleg Nesterov wrote: > > On 11/02, Oleg Nesterov wrote: > > > > On 11/02, Dmitry Vyukov wrote: > > > > > > But I wasn't able > > > to figure out what's the root cause (why task does not have > > > JOBCTL_STOP_PENDING) and maybe the same WARNING can be triggered > > > without root and/or

Re: WARNING in task_participate_group_stop

On 11/02, Oleg Nesterov wrote: > > On 11/02, Dmitry Vyukov wrote: > > > > But I wasn't able > > to figure out what's the root cause (why task does not have > > JOBCTL_STOP_PENDING) and maybe the same WARNING can be triggered > > without root and/or with other than init process. So still posting it

Re: WARNING in task_participate_group_stop

On 11/02, Dmitry Vyukov wrote: > > On Mon, Nov 2, 2015 at 4:13 PM, Oleg Nesterov wrote: > > Hi Dmitry, > > > > On 11/02, Dmitry Vyukov wrote: > >> > >> WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 > >> task_participate_group_stop+0x157/0x1d0() > >> Modules linked in: > >> CPU: 1 PID: 1 Comm:

Re: WARNING in task_participate_group_stop

On Mon, Nov 2, 2015 at 4:13 PM, Oleg Nesterov wrote: > Hi Dmitry, > > On 11/02, Dmitry Vyukov wrote: >> >> WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 >> task_participate_group_stop+0x157/0x1d0() >> Modules linked in: >> CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 >> Hardware name: QEMU

Re: WARNING in task_participate_group_stop

Hi Dmitry, On 11/02, Dmitry Vyukov wrote: > > WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 > task_participate_group_stop+0x157/0x1d0() > Modules linked in: > CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 >

WARNING in task_participate_group_stop

Hello, I've hit the following WARNING on 6a13feb9c82803e2b815eca72fa7a9f5561d7861 (4.3) [ cut here ] WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 task_participate_group_stop+0x157/0x1d0() Modules linked in: CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 Hardware name:

Re: WARNING in task_participate_group_stop

On 11/02, Oleg Nesterov wrote: > > On 11/02, Dmitry Vyukov wrote: > > > > But I wasn't able > > to figure out what's the root cause (why task does not have > > JOBCTL_STOP_PENDING) and maybe the same WARNING can be triggered > > without root and/or with other than init process. So still posting it

Re: WARNING in task_participate_group_stop

Hi Dmitry, On 11/02, Dmitry Vyukov wrote: > > WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 > task_participate_group_stop+0x157/0x1d0() > Modules linked in: > CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 >

Re: WARNING in task_participate_group_stop

On Mon, Nov 2, 2015 at 4:13 PM, Oleg Nesterov wrote: > Hi Dmitry, > > On 11/02, Dmitry Vyukov wrote: >> >> WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 >> task_participate_group_stop+0x157/0x1d0() >> Modules linked in: >> CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 >>

Re: WARNING in task_participate_group_stop

On 11/02, Dmitry Vyukov wrote: > > On Mon, Nov 2, 2015 at 4:13 PM, Oleg Nesterov wrote: > > Hi Dmitry, > > > > On 11/02, Dmitry Vyukov wrote: > >> > >> WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 > >> task_participate_group_stop+0x157/0x1d0() > >> Modules linked in: > >> CPU: 1

WARNING in task_participate_group_stop

Hello, I've hit the following WARNING on 6a13feb9c82803e2b815eca72fa7a9f5561d7861 (4.3) [ cut here ] WARNING: CPU: 1 PID: 1 at kernel/signal.c:334 task_participate_group_stop+0x157/0x1d0() Modules linked in: CPU: 1 PID: 1 Comm: init Not tainted 4.3.0 #48 Hardware name:

Re: WARNING in task_participate_group_stop

On 11/02, Oleg Nesterov wrote: > > On 11/02, Oleg Nesterov wrote: > > > > On 11/02, Dmitry Vyukov wrote: > > > > > > But I wasn't able > > > to figure out what's the root cause (why task does not have > > > JOBCTL_STOP_PENDING) and maybe the same WARNING can be triggered > > > without root and/or