From: syzbot <syzbot+607aa822c60b2e75b269@syzkaller.appspotmail.com>
To: agruenba@redhat.com, arnd@arndb.de, cluster-devel@redhat.com,
dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [gfs2?] kernel panic: hung_task: blocked tasks (2)
Date: Thu, 27 Jul 2023 16:14:29 -0700 [thread overview]
Message-ID: <00000000000045a44b0601802056@google.com> (raw)
In-Reply-To: <0000000000000cf7de0601056232@google.com>
syzbot has bisected this issue to:
commit 9c8ad7a2ff0bfe58f019ec0abc1fb965114dde7d
Author: David Howells <dhowells@redhat.com>
Date: Thu May 16 11:52:27 2019 +0000
uapi, x86: Fix the syscall numbering of the mount API syscalls [ver #2]
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=169b475ea80000
start commit: fdf0eaf11452 Linux 6.5-rc2
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=159b475ea80000
console output: https://syzkaller.appspot.com/x/log.txt?x=119b475ea80000
kernel config: https://syzkaller.appspot.com/x/.config?x=27e33fd2346a54b
dashboard link: https://syzkaller.appspot.com/bug?extid=607aa822c60b2e75b269
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11322fb6a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17687f1aa80000
Reported-by: syzbot+607aa822c60b2e75b269@syzkaller.appspotmail.com
Fixes: 9c8ad7a2ff0b ("uapi, x86: Fix the syscall numbering of the mount API syscalls [ver #2]")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-27 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 20:48 [syzbot] [gfs2?] kernel panic: hung_task: blocked tasks (2) syzbot
2023-07-27 23:14 ` syzbot [this message]
2023-07-28 8:20 ` David Howells
2023-07-28 11:48 ` Bob Peterson
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=00000000000045a44b0601802056@google.com \
--to=syzbot+607aa822c60b2e75b269@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=arnd@arndb.de \
--cc=cluster-devel@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).