[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000e5c94a05f65f130d@google.com>
Date: Wed, 08 Mar 2023 00:11:39 -0800
From: syzbot <syzbot+9fcea5ef6dc4dc72d334@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, dvyukov@...gle.com,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
nathan@...nel.org, ndesaulniers@...gle.com, ntfs3@...ts.linux.dev,
syzkaller-bugs@...glegroups.com, trix@...hat.com,
zengheng4@...wei.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in ntfs_listxattr
This bug is marked as fixed by commit:
ntfs: fix panic about slab-out-of-bounds caused by ntfs_listxattr()
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334
---
[1] I expect the commit to be present in:
1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
The full list of 10 trees can be found at
https://syzkaller.appspot.com/upstream/repos
Powered by blists - more mailing lists