From: syzbot <syzbot+6d7771315ecb9233f395@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] possible deadlock in __simple_recursive_removal
Date: Thu, 03 Jul 2025 04:08:05 -0700 [thread overview]
Message-ID: <68666495.050a0220.37fcff.0001.GAE@google.com> (raw)
In-Reply-To: <20250703092137.1888114-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6d7771315ecb9233f395@syzkaller.appspotmail.com
Tested-by: syzbot+6d7771315ecb9233f395@syzkaller.appspotmail.com
Tested on:
commit: 8d6c5833 Add linux-next specific files for 20250703
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17e40582580000
kernel config: https://syzkaller.appspot.com/x/.config?x=223eb69834aa2df6
dashboard link: https://syzkaller.appspot.com/bug?extid=6d7771315ecb9233f395
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=127ff982580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-07-03 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250703092137.1888114-1-lizhi.xu@windriver.com>
2025-07-03 11:08 ` syzbot [this message]
[not found] <20250703092424.1896345-1-lizhi.xu@windriver.com>
2025-07-03 11:15 ` [syzbot] [fs?] possible deadlock in __simple_recursive_removal syzbot
[not found] <20250703024914.1196577-1-lizhi.xu@windriver.com>
2025-07-03 9:24 ` syzbot
2025-07-02 18:04 syzbot
2025-07-02 18:39 ` Al Viro
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=68666495.050a0220.37fcff.0001.GAE@google.com \
--to=syzbot+6d7771315ecb9233f395@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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.