From: syzbot <syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] slab-out-of-bounds Read in mi_enum_attr
Date: Thu, 11 Jul 2024 00:17:10 -0700 [thread overview]
Message-ID: <0000000000001c15ec061cf38db5@google.com> (raw)
In-Reply-To: <00000000000012d4ed0610537e34@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: slab-out-of-bounds Read in mi_enum_attr
Author: almaz.alexandrovich@paragon-software.com
#syz test: https://github.com/Paragon-Software-Group/linux-ntfs3.git master
prev parent reply other threads:[~2024-07-11 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:17 [syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in mi_enum_attr syzbot
2024-02-02 2:49 ` [syzbot] " syzbot
2024-07-04 13:44 ` Dmitry Vyukov
2024-07-05 13:52 ` Lizhi Xu
2024-07-08 6:54 ` Dmitry Vyukov
2024-07-11 8:27 ` Konstantin Komarov
2024-08-20 10:53 ` lei lu
2024-02-02 3:33 ` [PATCH] fs/ntfs3: fix oob " Lizhi Xu
2024-07-11 7:16 ` [syzbot] slab-out-of-bounds Read " syzbot
2024-07-11 7:17 ` 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=0000000000001c15ec061cf38db5@google.com \
--to=syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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