From: syzbot <syzbot+bc79f8d1898960d41073@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, brauner@kernel.org,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
trix@redhat.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] KASAN: slab-use-after-free Read in ntfs_write_bh
Date: Tue, 26 Sep 2023 19:49:26 -0700 [thread overview]
Message-ID: <000000000000553a2106064e3d86@google.com> (raw)
In-Reply-To: <0000000000006777d506051db4fd@google.com>
syzbot has bisected this issue to:
commit 5f0fb2210bb34ecd3f7bfde0d8f0068b79b2e094
Author: Christoph Hellwig <hch@lst.de>
Date: Wed Aug 9 22:05:44 2023 +0000
ntfs3: don't call sync_blockdev in ntfs_put_super
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1671b51e680000
start commit: 6465e260f487 Linux 6.6-rc3
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1571b51e680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1171b51e680000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb54ecdfa197f132
dashboard link: https://syzkaller.appspot.com/bug?extid=bc79f8d1898960d41073
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14aa4e32680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171787b6680000
Reported-by: syzbot+bc79f8d1898960d41073@syzkaller.appspotmail.com
Fixes: 5f0fb2210bb3 ("ntfs3: don't call sync_blockdev in ntfs_put_super")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-27 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 23:29 [syzbot] [ntfs3?] KASAN: slab-use-after-free Read in ntfs_write_bh syzbot
2023-09-26 8:27 ` syzbot
2023-09-27 2:49 ` syzbot [this message]
2023-09-27 15:08 ` Christian Brauner
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=000000000000553a2106064e3d86@google.com \
--to=syzbot+bc79f8d1898960d41073@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.