From: syzbot ci <syzbot+ci6d0a047f2b211a66@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Fix warnings for RISC-V builds
Date: Sat, 28 Feb 2026 04:41:13 -0800 [thread overview]
Message-ID: <69a2e269.050a0220.3a55be.003e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] Fix warnings for RISC-V builds
https://lore.kernel.org/all/20260227152624.164964-1-seanwascoding@gmail.com
* [PATCH v4 1/2] sunrpc: fix unused variable warnings by using no_printk
* [PATCH v4 2/2] net: macb: use ethtool_sprintf to fill ethtool stats strings
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/aff67ec2-252a-44ec-9e63-cd30cea590b3
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: b9c8fc2caea6ff7e45c6942de8fee53515c66b34
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/f3072fa8-52cd-45e3-b797-cecafaf99df0/config
fs/nfsd/nfsfh.c:110:33: error: use of undeclared identifier 'buf'
fs/nfsd/nfsfh.c:110:45: error: use of undeclared identifier 'buf'
***
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:
[andrew@lunn.ch anna@kernel.org claudiu.beznea@tuxon.dev linux-kernel@vger.kernel.org linux-nfs@vger.kernel.org netdev@vger.kernel.org nicolas.ferre@microchip.com seanwascoding@gmail.com trond.myklebust@hammerspace.com]
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-28 12:41 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=69a2e269.050a0220.3a55be.003e.GAE@google.com \
--to=syzbot+ci6d0a047f2b211a66@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 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.