From: syzbot <syzbot+321477fad98ea6dd35b7@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] INFO: task hung in vfs_rename (2)
Date: Tue, 13 May 2025 09:15:02 -0700 [thread overview]
Message-ID: <68237006.050a0220.f2294.09fe.GAE@google.com> (raw)
In-Reply-To: <tencent_7CCE5C7B1E6DB02E756D609404E99EEEE20A@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+321477fad98ea6dd35b7@syzkaller.appspotmail.com
Tested-by: syzbot+321477fad98ea6dd35b7@syzkaller.appspotmail.com
Tested on:
commit: e9565e23 Merge tag 'sched_ext-for-6.15-rc6-fixes' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1668ecd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d3b7b9473eaace7
dashboard link: https://syzkaller.appspot.com/bug?extid=321477fad98ea6dd35b7
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=17544af4580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-05-13 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 21:28 [syzbot] [fs?] INFO: task hung in vfs_rename (2) syzbot
2025-04-23 11:35 ` Jan Kara
2025-05-13 12:00 ` Edward Adam Davis
2025-05-13 16:15 ` syzbot [this message]
2025-05-13 22:39 ` [PATCH] fs: Additional checks on new and old dir Edward Adam Davis
2025-05-16 19:31 ` Al Viro
2025-05-16 23:20 ` [pox on syzbot - again][exfat] exfat_mkdir() breakage on corrupted image Al Viro
2025-05-20 17:17 ` Aleksandr Nogikh
2025-07-22 17:51 ` [syzbot] [fs?] INFO: task hung in vfs_rename (2) Kent Overstreet
2025-07-23 8:38 ` Jan Kara
[not found] <20250423110503.4262-1-hdanton@sina.com>
2025-04-23 18:39 ` syzbot
[not found] <20250424110546.4284-1-hdanton@sina.com>
2025-04-24 12:01 ` syzbot
2025-04-24 19:51 ` 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=68237006.050a0220.f2294.09fe.GAE@google.com \
--to=syzbot+321477fad98ea6dd35b7@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--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.