From: syzbot <syzbot+e7be6bf3e45b7b463bfa@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
zlatistiv@gmail.com
Subject: Re: [syzbot] [bfs?] INFO: task hung in bfs_lookup (6)
Date: Mon, 20 Oct 2025 17:22:03 -0700 [thread overview]
Message-ID: <68f6d22b.a00a0220.18d35.0000.GAE@google.com> (raw)
In-Reply-To: <CAHjv_asXz7E0MyxJC1msGY0Jy2JmsYOZKDftL9v8MtCLJcoQWg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e7be6bf3e45b7b463bfa@syzkaller.appspotmail.com
Tested-by: syzbot+e7be6bf3e45b7b463bfa@syzkaller.appspotmail.com
Tested on:
commit: 6548d364 Merge tag 'cgroup-for-6.18-rc2-fixes' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=135943cd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=308983f9c02338e8
dashboard link: https://syzkaller.appspot.com/bug?extid=e7be6bf3e45b7b463bfa
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=10a77de2580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-21 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHjv_asXz7E0MyxJC1msGY0Jy2JmsYOZKDftL9v8MtCLJcoQWg@mail.gmail.com>
2025-10-21 0:22 ` syzbot [this message]
[not found] <CAHjv_au+-9FMB-XUZvRyHP=GVfAxEPN_N2Z6pyJV2=FpPAQEwA@mail.gmail.com>
2025-11-03 0:43 ` [syzbot] [bfs?] INFO: task hung in bfs_lookup (6) syzbot
[not found] <CAHjv_au2GAuojVcQcij5m4U4S0QYgqXXUV_hUUUGtD+3VMJXXA@mail.gmail.com>
2025-10-31 14:08 ` syzbot
[not found] <CAHjv_avAugj+r52YYT0i=OwOGTCEoEvQ5jWDhJj0mtTGmHGZqg@mail.gmail.com>
2025-10-30 22:29 ` syzbot
2025-09-17 22:54 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=68f6d22b.a00a0220.18d35.0000.GAE@google.com \
--to=syzbot+e7be6bf3e45b7b463bfa@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zlatistiv@gmail.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