From: Sabrina Dubroca <sd@queasysnail.net>
To: Antony Antony <antony.antony@secunet.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
devel@linux-ipsec.org, Leon Romanovsky <leon@kernel.org>,
Eyal Birger <eyal.birger@gmail.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH ipsec-next v6] xfrm: Add Direction to the SA in or out
Date: Fri, 5 Apr 2024 23:56:00 +0200 [thread overview]
Message-ID: <ZhBzcMrpBCNXXVBV@hog> (raw)
In-Reply-To: <a53333717022906933e9113980304fa4717118e9.1712320696.git.antony.antony@secunet.com>
Hi Antony,
2024-04-05, 14:40:07 +0200, Antony Antony wrote:
> This patch introduces the 'dir' attribute, 'in' or 'out', to the
> xfrm_state, SA, enhancing usability by delineating the scope of values
> based on direction. An input SA will now exclusively encompass values
> pertinent to input, effectively segregating them from output-related
> values.
But this patch isn't doing that for existing properties (I'm thinking
of replay window, not sure if any others are relevant [1]). Why not?
[1] that should include values passed via xfrm_usersa_info too,
not just XFRMA_* attributes
Adding these checks should be safe (wrt breakage of API): Old software
would not be passing XFRMA_SA_DIR, so adding checks when it is provided
would not break anything there. Only new software using the attribute
would benefit from having directed SAs and restriction on which attributes
can be used (and that's fine).
Right now the new attribute is 100% duplicate of the existing offload
direction, so I don't see much point.
> This change aims to streamline the configuration process and
> improve the overall clarity of SA attributes.
>
> This feature sets the groundwork for future patches, including
> the upcoming IP-TFS patch.
>
> Currently, dir is only allowed when HW OFFLOAD is set.
>
> ---
BTW, everything after this '---' will get cut, including your sign-off.
> v5->v6:
> - XFRMA_SA_DIR only allowed with HW OFFLOAD
>
> v4->v5:
> - add details to commit message
>
> v3->v4:
> - improve HW OFFLOAD DIR check check other direction
>
> v2->v3:
> - delete redundant XFRM_SA_DIR_USE
> - use u8 for "dir"
> - fix HW OFFLOAD DIR check
>
> v1->v2:
> - use .strict_start_type in struct nla_policy xfrma_policy
> - delete redundant XFRM_SA_DIR_MAX enum
> ---
>
> Signed-off-by: Antony Antony <antony.antony@secunet.com>
> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
nit: If I'm making non-trivial changes to the contents of the patch, I
typically drop the review (and test) tags I got on previous versions,
since they may no longer apply.
--
Sabrina
next prev parent reply other threads:[~2024-04-05 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:40 [PATCH ipsec-next v6] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-05 13:31 ` Nicolas Dichtel
2024-04-05 21:56 ` Sabrina Dubroca [this message]
2024-04-06 12:36 ` [devel-ipsec] " Christian Hopps
2024-04-07 8:23 ` Antony Antony
2024-04-08 13:02 ` Sabrina Dubroca
2024-04-09 17:23 ` Antony Antony
2024-04-10 8:56 ` Sabrina Dubroca
2024-04-10 16:59 ` Antony Antony
2024-04-10 21:41 ` Christian Hopps
2024-04-11 0:58 ` Paul Wouters
2024-04-11 9:23 ` Sabrina Dubroca
2024-04-11 11:03 ` Steffen Klassert
2024-04-11 9:24 ` Sabrina Dubroca
2024-04-11 10:36 ` Antony Antony
2024-04-11 20:14 ` Sabrina Dubroca
2024-04-11 10:57 ` Steffen Klassert
2024-04-10 6:27 ` Nicolas Dichtel
2024-04-10 7:26 ` Sabrina Dubroca
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=ZhBzcMrpBCNXXVBV@hog \
--to=sd@queasysnail.net \
--cc=antony.antony@secunet.com \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).