[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZtVwkW61Nkw0yTcA@gauss3.secunet.de>
Date: Mon, 2 Sep 2024 10:00:17 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Eyal Birger <eyal.birger@...il.com>
CC: <herbert@...dor.apana.org.au>, <davem@...emloft.net>,
<edumazet@...gle.com>, <kuba@...nel.org>, <dsahern@...nel.org>,
<pabeni@...hat.com>, <netdev@...r.kernel.org>, <devel@...ux-ipsec.org>
Subject: Re: [PATCH ipsec 0/2] xfrm: respect ip proto rules criteria in xfrm
dst lookups
On Sun, Sep 01, 2024 at 04:57:35PM -0700, Eyal Birger wrote:
> This series fixes the route lookup when done for xfrm to regard
> L4 criteria specified in ip rules.
>
> The first patch is a minor refactor to allow passing more parameters
> to dst lookup functions.
> The second patch actually passes L4 information to these lookup functions.
>
> Signed-off-by: Eyal Birger <eyal.birger@...il.com>
>
> Eyal Birger (2):
> xfrm: extract dst lookup parameters into a struct
> xfrm: respect ip protocols rules criteria when performing dst lookups
Hm, your patchset does not apply to the ipsec tree. Can you check
and rebase it?
Powered by blists - more mailing lists