From: syzbot <syzbot+4168fa4c45be33afa73c@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, axboe@kernel.dk,
christian.brauner@ubuntu.com, davem@davemloft.net,
ebiederm@xmission.com, fweisbec@gmail.com, hdanton@sina.com,
jmaloy@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, netdev@vger.kernel.org, oleg@redhat.com,
pcc@google.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tipc-discussion@lists.sourceforge.net,
tuong.t.lien@dektech.com.au, ying.xue@windriver.com
Subject: Re: INFO: rcu detected stall in sock_close (3)
Date: Fri, 15 Jan 2021 14:07:13 -0800 [thread overview]
Message-ID: <0000000000002ce11a05b8f7980a@google.com> (raw)
In-Reply-To: <0000000000005d946305a9f5d206@google.com>
syzbot suspects this issue was fixed by commit:
commit 98b89b649fce39dacb9dc036d6d0fdb8caff73f7
Author: Jens Axboe <axboe@kernel.dk>
Date: Fri Oct 9 22:03:01 2020 +0000
signal: kill JOBCTL_TASK_WORK
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b99c20d00000
start commit: 7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
dashboard link: https://syzkaller.appspot.com/bug?extid=4168fa4c45be33afa73c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112223b7100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154793a3100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: signal: kill JOBCTL_TASK_WORK
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-01-15 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000005d946305a9f5d206@google.com>
2020-07-20 7:08 ` INFO: rcu detected stall in sock_close (3) syzbot
2021-01-15 22:07 ` syzbot [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=0000000000002ce11a05b8f7980a@google.com \
--to=syzbot+4168fa4c45be33afa73c@syzkaller.appspotmail.com \
--cc=Markus.Elfring@web.de \
--cc=axboe@kernel.dk \
--cc=christian.brauner@ubuntu.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=hdanton@sina.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tuong.t.lien@dektech.com.au \
--cc=ying.xue@windriver.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;
as well as URLs for NNTP newsgroup(s).