From: syzbot <syzbot+0b7937459742a0a4cffd@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hch@lst.de, jack@suse.com,
jack@suse.cz, linkinjeon@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [udf?] KASAN: slab-use-after-free Read in udf_free_blocks
Date: Sat, 25 Nov 2023 03:54:03 -0800 [thread overview]
Message-ID: <000000000000b0cfb7060af8b9e1@google.com> (raw)
In-Reply-To: <000000000000d40c3c05fdc05cd1@google.com>
syzbot has bisected this issue to:
commit 36273e5b4e3a934c6d346c8f0b16b97e018094af
Author: Christoph Hellwig <hch@lst.de>
Date: Sun Nov 13 16:29:02 2022 +0000
udf: remove ->writepage
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14d71cece80000
start commit: 123212f53f3e Add linux-next specific files for 20230707
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16d71cece80000
console output: https://syzkaller.appspot.com/x/log.txt?x=12d71cece80000
kernel config: https://syzkaller.appspot.com/x/.config?x=15ec80b62f588543
dashboard link: https://syzkaller.appspot.com/bug?extid=0b7937459742a0a4cffd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15be1190a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d4666aa80000
Reported-by: syzbot+0b7937459742a0a4cffd@syzkaller.appspotmail.com
Fixes: 36273e5b4e3a ("udf: remove ->writepage")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-25 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 6:11 [syzbot] [udf?] KASAN: slab-use-after-free Read in udf_free_blocks syzbot
2023-11-25 11:54 ` syzbot [this message]
2023-11-25 13:10 ` syzbot
2024-03-02 15:19 ` syzbot
2024-03-11 9:25 ` Jan Kara
[not found] <tencent_F60445D778976B46CD3364E3732976A3AE05@qq.com>
2023-11-25 13:39 ` syzbot
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=000000000000b0cfb7060af8b9e1@google.com \
--to=syzbot+0b7937459742a0a4cffd@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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.