From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Paolo Abeni <pabeni@redhat.com>,
Jiayuan Chen <jiayuan.chen@linux.dev>,
netdev@vger.kernel.org
Cc: stable@vger.kernel.org, John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Ilya Lesokhin <ilyal@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
Boris Pismenny <borisp@mellanox.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v1] tls: device: fix out-of-bounds write in tls_append_frag()
Date: Tue, 25 Aug 2026 16:24:30 +0800 [thread overview]
Message-ID: <cbf1cf65-6f80-45ad-8b83-4927dd49c53c@linux.dev> (raw)
In-Reply-To: <b1ede30d-5c03-4514-980f-c656acf3bc13@redhat.com>
On 8/25/26 4:03 PM, Paolo Abeni wrote:
> On 8/23/26 10:47 AM, Jiayuan Chen wrote:
[...]
>> Fixes: e8f69799810c ("net/tls: Add generic NIC offload infrastructure")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
>>
>> ---
>> Hope to get capture attention
>>
>> netdevsim + tls (revised a lot locally):
>> https://lore.kernel.org/netdev/20260728125658.390500-1-jiayuan.chen@linux.dev/
> I must admit that RFC series have low chances of getting full attention
> these days, due to constant flood situation.
>
> Could you please re-submit that series formally?
>
> Thanks,
>
> Paolo
Thanks Paolo. Will do it after merge window.
next prev parent reply other threads:[~2026-08-25 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 8:47 [PATCH net v1] tls: device: fix out-of-bounds write in tls_append_frag() Jiayuan Chen
2026-08-25 8:03 ` Paolo Abeni
2026-08-25 8:24 ` Jiayuan Chen [this message]
2026-08-25 8:10 ` patchwork-bot+netdevbpf
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=cbf1cf65-6f80-45ad-8b83-4927dd49c53c@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ilyal@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
/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.