[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220428094319.04bf97fd@kernel.org>
Date: Thu, 28 Apr 2022 09:43:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, pabeni@...hat.com,
Leon Romanovsky <leonro@...dia.com>, netdev@...r.kernel.org,
Raed Salem <raeds@...dia.com>,
Shannon Nelson <snelson@...sando.io>,
Konrad Jankowski <konrad0.jankowski@...el.com>
Subject: Re: [PATCH net 1/1] ixgbe: ensure IPsec VF<->PF compatibility
On Wed, 27 Apr 2022 10:31:52 -0700 Tony Nguyen wrote:
> From: Leon Romanovsky <leonro@...dia.com>
>
> The VF driver can forward any IPsec flags and such makes the function
> is not extendable and prone to backward/forward incompatibility.
>
> If new software runs on VF, it won't know that PF configured something
> completely different as it "knows" only XFRM_OFFLOAD_INBOUND flag.
>
> Fixes: eda0333ac293 ("ixgbe: add VF IPsec management")
> Reviewed-by: Raed Salem <raeds@...dia.com>
> Signed-off-by: Leon Romanovsky <leonro@...dia.com>
> Reviewed-by: Shannon Nelson <snelson@...sando.io>
> Tested-by: Konrad Jankowski <konrad0.jankowski@...el.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@...el.com>
Commit f049efc7f7cd ("ixgbe: ensure IPsec VF<->PF compatibility") in
net, thanks!
Powered by blists - more mailing lists