From: syzbot <syzbot+bb950e68b400ab4f65f8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bigeasy@linutronix.de,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, peterz@infradead.org, pmladek@suse.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
valentin.schneider@arm.com
Subject: Re: [syzbot] INFO: rcu detected stall in snd_seq_write (2)
Date: Mon, 01 Nov 2021 01:54:12 -0700 [thread overview]
Message-ID: <0000000000001d3d6905cfb652d5@google.com> (raw)
In-Reply-To: <000000000000b4786c05cfa94612@google.com>
syzbot has bisected this issue to:
commit 1a7243ca4074beed97b68d7235a6e34862fc2cd6
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Tue Nov 10 11:38:47 2020 +0000
kthread: Move prio/affinite change into the newly created thread
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10b30e6ab00000
start commit: bdcc9f6a5682 Add linux-next specific files for 20211029
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12b30e6ab00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14b30e6ab00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b504bcb4c507265
dashboard link: https://syzkaller.appspot.com/bug?extid=bb950e68b400ab4f65f8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e913bab00000
Reported-by: syzbot+bb950e68b400ab4f65f8@syzkaller.appspotmail.com
Fixes: 1a7243ca4074 ("kthread: Move prio/affinite change into the newly created thread")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-11-01 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 17:20 [syzbot] INFO: rcu detected stall in snd_seq_write (2) syzbot
2021-11-01 8:54 ` 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=0000000000001d3d6905cfb652d5@google.com \
--to=syzbot+bb950e68b400ab4f65f8@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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