From: syzbot ci <syzbot+ci672dd867b4c4962f@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: nvme-tcp: Support receiving KeyUpdate requests
Date: Thu, 04 Sep 2025 20:32:16 -0700 [thread overview]
Message-ID: <68ba59c0.050a0220.192772.014f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] nvme-tcp: Support receiving KeyUpdate requests
https://lore.kernel.org/all/20250905024659.811386-1-alistair.francis@wdc.com
* [PATCH v2 1/7] net/handshake: Store the key serial number on completion
* [PATCH v2 2/7] net/handshake: Make handshake_req_cancel public
* [PATCH v2 3/7] net/handshake: Expose handshake_sk_destruct_req publically
* [PATCH v2 4/7] nvmet: Expose nvmet_stop_keep_alive_timer publically
* [PATCH v2 5/7] net/handshake: Support KeyUpdate message types
* [PATCH v2 6/7] nvme-tcp: Support KeyUpdate
* [PATCH v2 7/7] nvmet-tcp: Support KeyUpdate
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/6694796a-7c2c-4ef5-9055-cfff28bfd37b
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 5ef04a7b068cbb828eba226aacb42f880f7924d7
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/bf592b7e-e4da-4707-b710-d85d73fcfcee/config
drivers/nvme/target/tcp.c:1479:5: error: call to undeclared function 'update_tls_keys'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/nvme/target/tcp.c:1489:5: error: call to undeclared function 'update_tls_keys'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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:
[alistair.francis@wdc.com alistair23@gmail.com axboe@kernel.dk chuck.lever@oracle.com hare@kernel.org hch@lst.de kbusch@kernel.org kch@nvidia.com kernel-tls-handshake@lists.linux.dev linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-nfs@vger.kernel.org linux-nvme@lists.infradead.org netdev@vger.kernel.org sagi@grimberg.me]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-09-05 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 3:32 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 19:23 [moderation/CI] Re: nvme-tcp: Support receiving KeyUpdate requests syzbot ci
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=68ba59c0.050a0220.192772.014f.GAE@google.com \
--to=syzbot+ci672dd867b4c4962f@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