From: syzbot <syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in mi_enum_attr
Date: Thu, 11 Jul 2024 00:37:03 -0700 [thread overview]
Message-ID: <0000000000003398d5061cf3d49f@google.com> (raw)
In-Reply-To: <086e91b5-4afa-40e3-b8a6-f2734761f801@paragon-software.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com
Tested on:
commit: 9d9a2f29 Merge tag 'mm-hotfixes-stable-2024-07-10-13-1..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=106c2e9e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb254077242b0ab4
dashboard link: https://syzkaller.appspot.com/bug?extid=a426cde6dee8c2884b0b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-07-11 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <086e91b5-4afa-40e3-b8a6-f2734761f801@paragon-software.com>
2024-07-11 7:37 ` syzbot [this message]
[not found] <7bc3c0f4-d611-4328-b456-a7d2ac0ff4b9@paragon-software.com>
2024-07-11 7:57 ` [syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in mi_enum_attr syzbot
2024-07-04 13:44 [syzbot] " 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
[not found] <20240202024950.941119-1-lizhi.xu@windriver.com>
2024-02-02 3:16 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 15:17 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=0000000000003398d5061cf3d49f@google.com \
--to=syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.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