llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+9fcea5ef6dc4dc72d334@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, dvyukov@google.com,
	 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, zengheng4@huawei.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in ntfs_listxattr
Date: Wed, 03 May 2023 01:13:47 -0700	[thread overview]
Message-ID: <0000000000009bba0005fac5a2c6@google.com> (raw)
In-Reply-To: <000000000000ea3c3105ef377a12@google.com>

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

  parent reply	other threads:[~2023-05-03  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  7:00 [syzbot] KASAN: slab-out-of-bounds Read in ntfs_listxattr syzbot
2022-12-08  1:17 ` Zeng Heng
2023-03-08  8:11 ` syzbot
2023-03-22  8:12 ` syzbot
2023-04-05  8:12 ` syzbot
2023-04-19  8:13 ` syzbot
2023-05-03  8:13 ` syzbot [this message]
2023-05-12 14:07 ` [syzbot] [ntfs3?] " 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=0000000000009bba0005fac5a2c6@google.com \
    --to=syzbot+9fcea5ef6dc4dc72d334@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=dvyukov@google.com \
    --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=zengheng4@huawei.com \
    /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).