From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Ahern <dsahern@kernel.org>
Cc: <herbert@gondor.apana.org.au>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <netdev@vger.kernel.org>,
David Ahern <dahern@nvidia.com>
Subject: Re: [PATCH net-next] xfrm: Reject excessive values for XFRMA_TFCPAD
Date: Sat, 16 May 2026 10:02:04 +0200 [thread overview]
Message-ID: <aggkfHjZRge5j1lu@secunet.com> (raw)
In-Reply-To: <20260513165028.33171-1-dsahern@kernel.org>
On Wed, May 13, 2026 at 10:50:24AM -0600, David Ahern wrote:
> From: David Ahern <dahern@nvidia.com>
>
> tfcpad is a u32, but that full range is excessive for padding.
> Limit it to max IP length (64k).
>
> Signed-off-by: David Ahern <dahern@nvidia.com>
Also applied, thanks a lot!
prev parent reply other threads:[~2026-05-16 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:50 [PATCH net-next] xfrm: Reject excessive values for XFRMA_TFCPAD David Ahern
2026-05-16 8:02 ` Steffen Klassert [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=aggkfHjZRge5j1lu@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dahern@nvidia.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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