From: syzbot ci <syzbot+cie56250e034208490@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: tls: Add TLS 1.3 hardware offload support
Date: Wed, 21 Jan 2026 15:50:18 -0800 [thread overview]
Message-ID: <6971663a.050a0220.706b.001b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] tls: Add TLS 1.3 hardware offload support
https://lore.kernel.org/all/20260121215727.3994324-1-rjethwani@purestorage.com
* [PATCH v4 1/3] tls: add TLS 1.3 hardware offload support
* [PATCH v4 2/3] tls: add hardware offload key update support
* [PATCH v4 3/3] mlx5: TLS 1.3 hardware offload support
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4e064b47-6e51-4ca2-a937-7a06a90db567
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: d8f87aa5fa0a4276491fa8ef436cd22605a3f9ba
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/ecb421b3-d163-4e60-8ab7-1f94e8d55c45/config
net/tls/tls_device.c:1249:4: error: non-object type 'typeof (*sk->sk_validate_xmit_skb)' (aka 'struct sk_buff *(struct sock *, struct net_device *, struct sk_buff *)') is not assignable
***
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:
[borisp@nvidia.com davem@davemloft.net edumazet@google.com john.fastabend@gmail.com kuba@kernel.org leon@kernel.org mbloch@nvidia.com netdev@vger.kernel.org pabeni@redhat.com rjethwani@purestorage.com saeedm@nvidia.com sd@queasysnail.net tariqt@nvidia.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-01-21 23:50 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=6971663a.050a0220.706b.001b.GAE@google.com \
--to=syzbot+cie56250e034208490@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.