From: syzbot ci <syzbot+ci5cc2011ded9b4d74@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: kNFSD Signed Filehandles
Date: Tue, 24 Feb 2026 16:06:39 -0800 [thread overview]
Message-ID: <699e3d0f.a00a0220.21906d.0000.GAE@google.com> (raw)
syzbot ci has tested the following series
[v7] kNFSD Signed Filehandles
https://lore.kernel.org/all/cover.1771961922.git.bcodding@hammerspace.com
* [PATCH v7 1/3] NFSD: Add a key for signing filehandles
* [PATCH v7 2/3] NFSD/export: Add sign_fh export option
* [PATCH v7 3/3] NFSD: Sign filehandles
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/6f7fbcf9-bd00-4b5e-b15c-5eb49fdc6255
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 7dff99b354601dd01829e1511711846e04340a69
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/dafdda14-c64a-42e4-b492-e96c8c81adca/config
fs/nfsd/nfsfh.c:196:13: error: redefinition of 'fh_append_mac'
fs/nfsd/nfsfh.c:228:13: error: redefinition of 'fh_verify_mac'
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[anna@kernel.org bcodding@hammerspace.com chuck.lever@oracle.com ebiggers@kernel.org jlayton@kernel.org linux-crypto@vger.kernel.org linux-fsdevel@vger.kernel.org linux-nfs@vger.kernel.org neil@brown.name rick.macklem@gmail.com trondmy@kernel.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-25 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=699e3d0f.a00a0220.21906d.0000.GAE@google.com \
--to=syzbot+ci5cc2011ded9b4d74@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox