From: syzbot <syzbot+6b16e3d085833cbf3e25@syzkaller.appspotmail.com>
To: jchuang26@m.fudan.edu.cn, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] KASAN: slab-use-after-free Write in config_item_get
Date: Fri, 11 Sep 2026 01:44:03 -0700 [thread overview]
Message-ID: <6aa3bf53.6e6c5f9e.28f11f.0042.GAE@google.com> (raw)
In-Reply-To: <6aa3b8a3.df8406c6.e4681.4ae6SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6b16e3d085833cbf3e25@syzkaller.appspotmail.com
Tested-by: syzbot+6b16e3d085833cbf3e25@syzkaller.appspotmail.com
Tested on:
commit: a7c1290e configfs: pin the symlink target's dirent ins..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=140d21f9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d794b10c2a1184e
dashboard link: https://syzkaller.appspot.com/bug?extid=6b16e3d085833cbf3e25
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=10782601580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-09-11 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aa3b8a3.df8406c6.e4681.4ae6SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-11 8:44 ` syzbot [this message]
[not found] <6aa74ffd.2cd27cd2.290120.3dbeSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 2:03 ` [syzbot] [fs?] KASAN: slab-use-after-free Write in config_item_get syzbot
[not found] <6aa3ec49.faa14f7e.2f7ba7.7c6fSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-11 13:16 ` syzbot
[not found] <SI2PR03MB564251F6E74EDBC70B1BA6C5C0BF2@SI2PR03MB5642.apcprd03.prod.outlook.com>
2026-09-10 12:47 ` syzbot
2026-07-30 0:19 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=6aa3bf53.6e6c5f9e.28f11f.0042.GAE@google.com \
--to=syzbot+6b16e3d085833cbf3e25@syzkaller.appspotmail.com \
--cc=jchuang26@m.fudan.edu.cn \
--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 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.