Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	sd@queasysnail.net, john.fastabend@gmail.com, shuah@kernel.org,
	cel@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/5] net: tls: break the connection after a burst of empty data records
Date: Thu, 12 Nov 2026 19:20:06 +0000	[thread overview]
Message-ID: <179451120678.604801.8398607800818615102.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111185522.2859004-1-kuba@kernel.org>

Hello:

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

On Wed, 11 Nov 2026 10:55:17 -0800 you wrote:
> Deal with overload of zero-length TLS records. This is the next iteration
> of Chuck's series. I tried to make it as simple as possible - break the
> connection if sender floods us with zero-length records. Consume / discard
> those records even on PEEK to avoid infinite rx_list growth.
> 
> https://lore.kernel.org/20261019-tls-follow-on-v6-0-ab01c4ecca0c@kernel.org
> 
> [...]

Here is the summary with links:
  - [net,v2,1/5] tls: Break the connection after a burst of empty data records
    https://git.kernel.org/netdev/net/c/201f0531e413
  - [net,v2,2/5] tls: Consume empty data records in tls_sw_splice_read()
    https://git.kernel.org/netdev/net/c/db6a6c6863bd
  - [net,v2,3/5] selftests: tls: Skip the zero_len tests when TLS is unavailable
    https://git.kernel.org/netdev/net/c/77389a6d30a2
  - [net,v2,4/5] selftests: tls: Extend coverage for zero-length records
    https://git.kernel.org/netdev/net/c/512f2cb73664
  - [net,v2,5/5] selftests: tls: Cover the cap on consecutive empty records
    https://git.kernel.org/netdev/net/c/e6dfa7bfdf15

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-12 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 18:55 [PATCH net v2 0/5] net: tls: break the connection after a burst of empty data records Jakub Kicinski
2026-11-11 18:55 ` [PATCH net v2 1/5] tls: Break " Jakub Kicinski
2026-11-11 18:55 ` [PATCH net v2 2/5] tls: Consume empty data records in tls_sw_splice_read() Jakub Kicinski
2026-11-11 18:55 ` [PATCH net v2 3/5] selftests: tls: Skip the zero_len tests when TLS is unavailable Jakub Kicinski
2026-11-11 18:55 ` [PATCH net v2 4/5] selftests: tls: Extend coverage for zero-length records Jakub Kicinski
2026-11-11 18:55 ` [PATCH net v2 5/5] selftests: tls: Cover the cap on consecutive empty records Jakub Kicinski
2026-11-12 19:20 ` 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=179451120678.604801.8398607800818615102.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cel@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox