From: Sabrina Dubroca <sd@queasysnail.net>
To: tanjingguo <tanjingguo@huawei.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chenzhe <chenzhe@huawei.com>, "malin (R)" <malin89@huawei.com>,
michenyuan <michenyuan@huawei.com>,
cenxianlong <cenxianlong@huawei.com>,
"steffen.klassert@secunet.com" <steffen.klassert@secunet.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"dsahern@kernel.org" <dsahern@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>
Subject: Re: [PATCH ipsec v2] xfrm: esp: restore combined single-frag length gate
Date: Thu, 21 May 2026 15:15:02 +0200 [thread overview]
Message-ID: <ag8FVjyh2ZoYuSbR@krikkit> (raw)
In-Reply-To: <ab4c5808478d48978292c318d85c4484@huawei.com>
Note that you must respect a 24-hour delay between reposts of the same
patch:
https://docs.kernel.org/process/maintainer-netdev.html#tl-dr
2026-05-21, 12:00:55 +0000, tanjingguo wrote:
> Changes in v2:
> - Use the ipsec tree subject prefix.
> - Clarify that esp_output_tail() allocates after esp_output_head() appends
> tailen.
Thanks for the clarification.
> - Avoid shadowing the existing allocsize variable.
> - v1: https://lore.kernel.org/netdev/ag7kxJ39XQaVY1Mb@krikkit/T/#t
>
> net/ipv4/esp4.c | 4 ++--
> net/ipv6/esp6.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/net/ipv4/esp4.c b/net/ipv4/esp4.c
> index 6a5febbdbee49..c62dfe049ee7 100644
> --- a/net/ipv4/esp4.c
> +++ b/net/ipv4/esp4.c
> @@ -419,8 +419,8 @@ int esp_output_head(struct xfrm_state *x, struct sk_buff *skb, struct esp_info *
> return err;
> }
>
> - if (ALIGN(tailen, L1_CACHE_BYTES) > PAGE_SIZE ||
> - ALIGN(skb->data_len, L1_CACHE_BYTES) > PAGE_SIZE)
> + if (ALIGN(skb->data_len + tailen, L1_CACHE_BYTES) >
> + PAGE_SIZE)
> goto cow;
nit: you didn't need to wrap here, the total length of this line is
under 80 columns.
But other than that, the fix looks correct to me:
Reviewed-by: Sabrina Dubroca <sd@queasysnail.net>
I don't know if Steffen will require a repost or apply this directly,
so please wait at least the standard 24 hours.
Thanks,
--
Sabrina
prev parent reply other threads:[~2026-05-21 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 12:00 [PATCH ipsec v2] xfrm: esp: restore combined single-frag length gate tanjingguo
2026-05-21 13:15 ` Sabrina Dubroca [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=ag8FVjyh2ZoYuSbR@krikkit \
--to=sd@queasysnail.net \
--cc=cenxianlong@huawei.com \
--cc=chenzhe@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malin89@huawei.com \
--cc=michenyuan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=tanjingguo@huawei.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