From: syzbot <syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tao1.yu@intel.com
Subject: Re: [syzbot] [block?] [cgroups?] possible deadlock in blkg_conf_prep
Date: Sun, 30 Aug 2026 22:43:01 -0700 [thread overview]
Message-ID: <6a951465.a8e469d2.cbf3.5613.GAE@google.com> (raw)
In-Reply-To: <f1e20018-8314-4400-9c73-d0a3b972eb0fn@googlegroups.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com
Tested-by: syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com
Tested on:
commit: 3cf7d328 blk-cgroup: use GFP_NOIO for radix tree prelo..
git tree: https://github.com/yutao-intel/linux.git fix-linux-next-block-blk-cgroups
console output: https://syzkaller.appspot.com/x/log.txt?x=134e6379580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=144a1c0e22e53a08ef5a
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-08-31 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f1e20018-8314-4400-9c73-d0a3b972eb0fn@googlegroups.com>
2026-08-31 5:43 ` syzbot [this message]
[not found] <96064883-7d31-4ba9-b849-bc29f734afcan@googlegroups.com>
2026-08-31 3:50 ` syzbot
[not found] <db1a2ef9-0e68-4461-8fbf-b4e37093f24an@googlegroups.com>
2026-08-31 3:17 ` syzbot
2026-08-15 14:47 syzbot
2026-08-21 9:20 ` syzbot
2026-08-29 0:33 ` 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=6a951465.a8e469d2.cbf3.5613.GAE@google.com \
--to=syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tao1.yu@intel.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
all inboxes | Powered by JetHome®