All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
	john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
	davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
	horms@kernel.org, aviadye@mellanox.com, borisp@mellanox.com,
	ilyal@mellanox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5 1/2] tls: only install push_pending_record for a TX context
Date: Tue, 10 Nov 2026 19:50:06 +0000	[thread overview]
Message-ID: <179434020617.26472.10011762273074011911.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102213011.4191020-1-rjethwani@purestorage.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  2 Nov 2026 14:30:06 -0700 you wrote:
> tls_set_sw_offload() assigns ctx->push_pending_record for both
> directions, but the hook is a TX-side dispatcher. On a socket whose TX
> side is HW offloaded, tls_set_device_offload() installs
> tls_device_push_pending_record(); any later TLS_RX setsockopt
> overwrites it with tls_sw_push_pending_record(), because
> tls_set_device_offload_rx() itself calls tls_set_sw_offload(sk, 0, NULL)
> for the software half of a successful HW RX offload, and so does the
> fallback when the RX offload is declined (NIC with TX-only offload,
> tls_dev_add() failure).
> 
> [...]

Here is the summary with links:
  - [net,v5,1/2] tls: only install push_pending_record for a TX context
    https://git.kernel.org/netdev/net/c/c47e766c5307
  - [net,v5,2/2] selftests: net: add TLS 1.2 hardware offload tests
    https://git.kernel.org/netdev/net/c/ec7b283e11e4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-10 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 21:30 [PATCH net v5 1/2] tls: only install push_pending_record for a TX context Rishikesh Jethwani
2026-11-02 21:30 ` [PATCH net v5 2/2] selftests: net: add TLS 1.2 hardware offload tests Rishikesh Jethwani
2026-11-03 21:33   ` netdev-bot+sashiko
2026-11-04 18:20     ` Rishikesh Jethwani
2026-11-10 19:50 ` patchwork-bot+netdevbpf [this message]

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=179434020617.26472.10011762273074011911.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --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=rjethwani@purestorage.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.