From: Oleg Nesterov <oleg@redhat.com>
To: syzbot <syzbot+b109633ea805cac54a61@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, ebiederm@xmission.com,
ldv@altlinux.org, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: WARNING in task_participate_group_stop (2)
Date: Mon, 30 Apr 2018 15:22:32 +0200 [thread overview]
Message-ID: <20180430132232.GA7990@redhat.com> (raw)
In-Reply-To: <0000000000001490fb056affabd8@google.com>
On 04/29, syzbot wrote:
>
> RIP: 0010:task_participate_group_stop+0x205/0x260 kernel/signal.c:351
> RSP: 0018:ffff8801ae7b7880 EFLAGS: 00010093
> RAX: ffff8801d96200c0 RBX: 0000000000000000 RCX: ffffffff81498b5b
> RDX: 0000000000000000 RSI: ffffffff81498c75 RDI: 0000000000000005
> RBP: ffff8801ae7b78a0 R08: ffff8801d96200c0 R09: ffffed0036c48971
> R10: ffffed0036c48971 R11: ffff8801b6244b8b R12: ffff8801d926ecd8
> R13: ffff8801d926ec40 R14: 0000000000040000 R15: dffffc0000000000
> do_signal_stop+0x502/0xa20 kernel/signal.c:2176
> get_signal+0x9b4/0x1960 kernel/signal.c:2353
> do_signal+0x98/0x2040 arch/x86/kernel/signal.c:810
> exit_to_usermode_loop+0x28a/0x310 arch/x86/entry/common.c:162
> prepare_exit_to_usermode arch/x86/entry/common.c:196 [inline]
> syscall_return_slowpath arch/x86/entry/common.c:265 [inline]
> do_syscall_64+0x6ac/0x800 arch/x86/entry/common.c:290
> entry_SYSCALL_64_after_hwframe+0x49/0xbe
Thanks... I need to think and recall how this code works, but at first glance
zap_other_threads() needs task_clear_jobctl_pending(current).
I am almost sure the warning should go away, but iiuc there are more problems
and it is not clear to me what can we do...
Oleg.
prev parent reply other threads:[~2018-04-30 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 17:00 syzbot
2018-04-30 13:22 ` Oleg Nesterov [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=20180430132232.GA7990@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=syzbot+b109633ea805cac54a61@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome