From: syzbot <syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com>
To: hrushirajg23@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] KASAN: slab-use-after-free Read in debugfs_u32_get (2)
Date: Thu, 18 Jun 2026 06:40:02 -0700 [thread overview]
Message-ID: <6a33f532.537e895e.3cc275.0004.GAE@google.com> (raw)
In-Reply-To: <20260618131218.300241-1-hrushirajg23@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com
Tested-by: syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com
Tested on:
commit: e771677c Merge tag 'for-linus-iommufd' of git://git.ke..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14ce93b6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea349aa18d06ec5e
dashboard link: https://syzkaller.appspot.com/bug?extid=6c25f4750230faf70be9
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=110e93b6580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-06-18 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260618131218.300241-1-hrushirajg23@gmail.com>
2026-06-18 13:40 ` syzbot [this message]
[not found] <20260627051704.8867-1-hrushirajg23@gmail.com>
2026-06-27 6:23 ` syzbot
[not found] <20260618123427.291695-1-hrushirajg23@gmail.com>
2026-06-18 12:59 ` syzbot
[not found] <20260618090148.266462-1-hrushirajg23@gmail.com>
2026-06-18 9:24 ` syzbot
[not found] <CAEo+JPr5wc2d6DiTG3pxqHeFSKg9kRMQnpTL8dKhqdWxmxGAVA@mail.gmail.com>
2026-06-18 8:58 ` syzbot
[not found] <CAEo+JPpZtu=U1+LH=Thow9a6xUfvBtS_f3_B__rrHy0+5fScVg@mail.gmail.com>
2026-06-18 7:47 ` syzbot
2026-06-17 18:35 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=6a33f532.537e895e.3cc275.0004.GAE@google.com \
--to=syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com \
--cc=hrushirajg23@gmail.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