From: syzbot <syzbot+512459401510e2a9a39f@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
wangqing7171@gmail.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in filename_rmdir
Date: Sat, 28 Feb 2026 01:02:02 -0800 [thread overview]
Message-ID: <69a2af0a.050a0220.3a55be.0036.GAE@google.com> (raw)
In-Reply-To: <20260228082942.1853224-1-wangqing7171@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+512459401510e2a9a39f@syzkaller.appspotmail.com
Tested-by: syzbot+512459401510e2a9a39f@syzkaller.appspotmail.com
Tested on:
commit: 4d349ee5 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14b7f1aa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=70fe0401f305d8d4
dashboard link: https://syzkaller.appspot.com/bug?extid=512459401510e2a9a39f
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=14d62202580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-02-28 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 13:49 [syzbot] [ext4?] INFO: task hung in filename_rmdir syzbot
2026-02-28 8:29 ` Qing Wang
2026-02-28 9:02 ` syzbot [this message]
2026-02-28 9:44 ` Qing Wang
2026-03-01 8:35 ` Edward Adam Davis
2026-03-01 9:09 ` syzbot
2026-03-05 4:51 ` Edward Adam Davis
2026-03-05 5:33 ` syzbot
2026-03-05 6:35 ` Edward Adam Davis
2026-03-05 7:08 ` syzbot
2026-03-05 12:21 ` Edward Adam Davis
2026-03-05 14:11 ` syzbot
2026-03-06 1:18 ` Edward Adam Davis
2026-03-06 2:20 ` 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=69a2af0a.050a0220.3a55be.0036.GAE@google.com \
--to=syzbot+512459401510e2a9a39f@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wangqing7171@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 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.