From: syzbot <syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, nooraineqbal@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-out-of-bounds Read in change_page_attr_set_clr
Date: Mon, 29 Sep 2025 02:27:02 -0700 [thread overview]
Message-ID: <68da50e6.a70a0220.10c4b.002b.GAE@google.com> (raw)
In-Reply-To: <20250929075024.115993-1-nooraineqbal@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com
Tested-by: syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com
Tested on:
commit: 26285807 Add linux-next specific files for 20250926
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14afeae2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=997066872b7941b6
dashboard link: https://syzkaller.appspot.com/bug?extid=e34177f6091df113ef20
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=114d2ae2580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-29 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250929075024.115993-1-nooraineqbal@gmail.com>
2025-09-29 9:27 ` syzbot [this message]
[not found] <20250913073552.192945-1-chandna.linuxkernel@gmail.com>
2025-09-13 8:58 ` [syzbot] [kernel?] KASAN: slab-out-of-bounds Read in change_page_attr_set_clr syzbot
[not found] <41049daa-ffa1-42d8-9935-c56e02344afb@gmail.com>
2025-09-13 5:21 ` syzbot
2025-09-03 17:36 syzbot
2025-10-20 9:16 ` syzbot
2025-10-20 23:21 ` Dave Hansen
2025-11-19 21:32 ` 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=68da50e6.a70a0220.10c4b.002b.GAE@google.com \
--to=syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nooraineqbal@gmail.com \
--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