From: syzbot ci <syzbot+ci3c02e9f7322a9ff3@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: Wed, 04 Mar 2026 11:23:10 -0800 [thread overview]
Message-ID: <69a8869e.050a0220.21ae90.001a.GAE@google.com> (raw)
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
next reply other threads:[~2026-03-04 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 19:23 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 3:32 [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=69a8869e.050a0220.21ae90.001a.GAE@google.com \
--to=syzbot+ci3c02e9f7322a9ff3@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