From: syzbot <syzbot+9eefe09bedd093f156c2@syzkaller.appspotmail.com>
To: david.hunter.linux@gmail.com, kartikey406@gmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfs?] WARNING in nsfs_fh_to_dentry
Date: Sat, 20 Sep 2025 23:03:03 -0700 [thread overview]
Message-ID: <68cf9517.050a0220.13cd81.002b.GAE@google.com> (raw)
In-Reply-To: <20250921052315.836564-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9eefe09bedd093f156c2@syzkaller.appspotmail.com
Tested-by: syzbot+9eefe09bedd093f156c2@syzkaller.appspotmail.com
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=127fa712580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
dashboard link: https://syzkaller.appspot.com/bug?extid=9eefe09bedd093f156c2
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=16ff1534580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-09-21 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 5:23 [PATCH] nsfs: reject file handles with invalid inode number Deepanshu Kartikey
2025-09-21 6:03 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-21 3:18 Deepanshu Kartikey
2025-09-21 3:44 ` [syzbot] [nfs?] WARNING in nsfs_fh_to_dentry syzbot
2025-09-21 0:53 [PATCH] nsfs: validate file handle type and data in nsfs_fh_to_dentry() Deepanshu Kartikey
2025-09-21 2:14 ` [syzbot] [nfs?] WARNING in nsfs_fh_to_dentry syzbot
2025-09-20 8:11 [PATCH] nsfs: validate file handle type in nsfs_fh_to_dentry() Deepanshu Kartikey
2025-09-20 8:36 ` [syzbot] [nfs?] WARNING in nsfs_fh_to_dentry syzbot
2025-09-20 0:13 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=68cf9517.050a0220.13cd81.002b.GAE@google.com \
--to=syzbot+9eefe09bedd093f156c2@syzkaller.appspotmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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.