From: Sabrina Dubroca <sd@queasysnail.net>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: antony.antony@secunet.com,
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>
Subject: Re: [PATCH ipsec-next v9] xfrm: Add Direction to the SA in or out
Date: Wed, 10 Apr 2024 10:57:20 +0200 [thread overview]
Message-ID: <ZhZUcNKD8viY6Y3W@hog> (raw)
In-Reply-To: <1909116d-15e1-48ac-ab55-21bce409fe64@6wind.com>
2024-04-10, 10:37:27 +0200, Nicolas Dichtel wrote:
> Le 10/04/2024 à 10:17, Sabrina Dubroca a écrit :
> [snip]
> >> Why isn't it possible to restrict the use of an input SA to the input path and
> >> output SA to xmit path?
> >
> > Because nobody has written a patch for it yet :)
> >
> For me, it should be done in this patch/series ;-)
Sounds good to me.
--
Sabrina
next prev parent reply other threads:[~2024-04-10 8:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 17:56 [PATCH ipsec-next v9] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-10 6:32 ` Nicolas Dichtel
2024-04-10 7:26 ` Sabrina Dubroca
2024-04-10 7:35 ` Nicolas Dichtel
2024-04-10 8:17 ` Sabrina Dubroca
2024-04-10 8:37 ` Nicolas Dichtel
2024-04-10 8:57 ` Sabrina Dubroca [this message]
2024-04-10 13:52 ` [devel-ipsec] " Paul Wouters
2024-04-11 7:23 ` Steffen Klassert
2024-04-11 7:22 ` Steffen Klassert
2024-04-11 9:05 ` Nicolas Dichtel
2024-04-11 9:31 ` Steffen Klassert
2024-04-11 7:14 ` Steffen Klassert
2024-04-11 9:01 ` Nicolas Dichtel
2024-04-11 9:04 ` Steffen Klassert
2024-04-11 9:36 ` Antony Antony
2024-04-11 9:35 ` Antony Antony
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=ZhZUcNKD8viY6Y3W@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