From: syzbot <syzbot+3e719fc23ab95580e4c2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org,
bvanassche@acm.org, cascardo@igalia.com, chao@kernel.org,
hughd@google.com, josef@toxicpanda.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, rdunlap@infradead.org, sandeen@redhat.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
willy@infradead.org
Subject: Re: [syzbot] [hfs?] [mm?] KASAN: slab-out-of-bounds Write in shmem_file_read_iter
Date: Fri, 06 Dec 2024 06:16:03 -0800 [thread overview]
Message-ID: <67530723.050a0220.a30f1.013f.GAE@google.com> (raw)
In-Reply-To: <000000000000d69fc4060c7d50a2@google.com>
syzbot suspects this issue was fixed by commit:
commit 1c82587cb57687de3f18ab4b98a8850c789bedcf
Author: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Date: Thu Nov 7 11:41:09 2024 +0000
hfsplus: don't query the device logical block size multiple times
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=174098df980000
start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4d90a36f0cab495a
dashboard link: https://syzkaller.appspot.com/bug?extid=3e719fc23ab95580e4c2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14903769180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f25d81180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: hfsplus: don't query the device logical block size multiple times
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-06 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 19:30 [syzbot] [mm?] [hfs?] " syzbot
2024-12-06 14:16 ` 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=67530723.050a0220.a30f1.013f.GAE@google.com \
--to=syzbot+3e719fc23ab95580e4c2@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=cascardo@igalia.com \
--cc=chao@kernel.org \
--cc=hughd@google.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sandeen@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox