* [moderation/CI] Re: nvme-tcp: Support receiving KeyUpdate requests
@ 2025-09-05 3:32 syzbot ci
0 siblings, 0 replies; 2+ messages in thread
From: syzbot ci @ 2025-09-05 3:32 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [moderation/CI] Re: nvme-tcp: Support receiving KeyUpdate requests
@ 2026-03-04 19:23 syzbot ci
0 siblings, 0 replies; 2+ messages in thread
From: syzbot ci @ 2026-03-04 19:23 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v7] nvme-tcp: Support receiving KeyUpdate requests
https://lore.kernel.org/all/20260304053500.590630-1-alistair.francis@wdc.com
* [PATCH v7 1/5] net/handshake: Store the key serial number on completion
* [PATCH v7 2/5] net/handshake: Define handshake_req_keyupdate
* [PATCH v7 3/5] net/handshake: Support KeyUpdate message types
* [PATCH v7 4/5] nvme-tcp: Support KeyUpdate
* [PATCH v7 5/5] nvmet-tcp: Support KeyUpdate
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ea1ac81d-ad9c-4af0-a8dc-9f48ff663c44
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 4ff5801f45b494ad8251a16ec06c9f303ed3b9a0
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/cafaf057-8306-41c8-9ed4-ebfd3bc0323a/config
drivers/nvme/host/tcp.c:1429:24: error: no member named 'read_sock_cmsg' in 'struct proto_ops'
***
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 hare@suse.de 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
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-03-04 19:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-05 3:32 [moderation/CI] Re: nvme-tcp: Support receiving KeyUpdate requests syzbot ci
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 19:23 syzbot ci
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox