From: syzbot <syzbot+662f87a8ef490f45fa64@syzkaller.appspotmail.com>
To: autofs@vger.kernel.org, billodo@redhat.com, bodonnel@redhat.com,
brauner@kernel.org, eadavis@qq.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
raven@themaw.net, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [autofs?] general protection fault in autofs_fill_super
Date: Thu, 16 Nov 2023 01:51:09 -0800 [thread overview]
Message-ID: <00000000000096e7d5060a41f594@google.com> (raw)
In-Reply-To: <000000000000ae5995060a125650@google.com>
syzbot has bisected this issue to:
commit e6ec453bd0f03a60a80f00f95ae2eaa260faa3c2
Author: Ian Kent <raven@themaw.net>
Date: Fri Sep 22 04:12:14 2023 +0000
autofs: convert autofs to use the new mount api
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d04220e80000
start commit: 4bbdb725a36b Merge tag 'iommu-updates-v6.7' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11d04220e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=16d04220e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=beb32a598fd79db9
dashboard link: https://syzkaller.appspot.com/bug?extid=662f87a8ef490f45fa64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14384a7b680000
Reported-by: syzbot+662f87a8ef490f45fa64@syzkaller.appspotmail.com
Fixes: e6ec453bd0f0 ("autofs: convert autofs to use the new mount api")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-16 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 1:02 [syzbot] [autofs?] general protection fault in autofs_fill_super syzbot
2023-11-14 3:52 ` [PATCH] autofs: fix null deref " Edward Adam Davis
2023-11-14 4:25 ` Ian Kent
2023-11-14 4:41 ` Al Viro
2023-11-14 8:30 ` Ian Kent
2023-11-14 15:26 ` Al Viro
2023-11-15 0:18 ` Ian Kent
2023-11-15 0:35 ` Al Viro
2023-11-15 1:06 ` Ian Kent
2023-11-14 5:48 ` [PATCH V2] autofs: fix null ptr " Edward Adam Davis
2023-11-16 9:51 ` 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=00000000000096e7d5060a41f594@google.com \
--to=syzbot+662f87a8ef490f45fa64@syzkaller.appspotmail.com \
--cc=autofs@vger.kernel.org \
--cc=billodo@redhat.com \
--cc=bodonnel@redhat.com \
--cc=brauner@kernel.org \
--cc=eadavis@qq.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--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).