From: syzbot <syzbot+8ebb469b64740648f1c3@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
edward.lo@ambergroup.io, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in mi_find_attr
Date: Tue, 31 Jan 2023 01:27:17 -0800 [thread overview]
Message-ID: <000000000000171a2805f38bf07a@google.com> (raw)
In-Reply-To: <000000000000d7eced05f01fa8d0@google.com>
syzbot suspects this issue was fixed by commit:
commit 4f1dc7d9756e66f3f876839ea174df2e656b7f79
Author: Edward Lo <edward.lo@ambergroup.io>
Date: Fri Sep 9 01:04:00 2022 +0000
fs/ntfs3: Validate attribute name offset
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12e74535480000
start commit: e2ca6ba6ba01 Merge tag 'mm-stable-2022-12-13' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a6133b41a9a0f500
dashboard link: https://syzkaller.appspot.com/bug?extid=8ebb469b64740648f1c3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16fb2ad0480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164513e0480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Validate attribute name offset
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-31 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 20:00 [syzbot] KASAN: slab-out-of-bounds Read in mi_find_attr syzbot
2023-01-19 9:35 ` syzbot
2023-01-31 9:27 ` syzbot [this message]
2023-02-01 7:54 ` Dmitry Vyukov
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=000000000000171a2805f38bf07a@google.com \
--to=syzbot+8ebb469b64740648f1c3@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=edward.lo@ambergroup.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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.