From: Leon Romanovsky <leon@kernel.org>
To: Shannon Nelson <snelson@pensando.io>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
intel-wired-lan@lists.osuosl.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>, Raed Salem <raeds@nvidia.com>,
Shannon Nelson <shannon.nelson@oracle.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH net] ixgbe: ensure IPsec VF<->PF compatibility
Date: Thu, 31 Mar 2022 10:45:10 +0300 [thread overview]
Message-ID: <YkVcBgac41VjNBd7@unreal> (raw)
In-Reply-To: <b201a3ed-5698-4e91-adc9-34c938e43668@pensando.io>
On Wed, Mar 30, 2022 at 09:13:21AM -0700, Shannon Nelson wrote:
> On 3/30/22 4:01 AM, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.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@nvidia.com>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > ---
> > There is no simple fix for this VF/PF incompatibility as long as FW
> > doesn't filter/decline unsupported options when convey mailbox from VF
> > to PF.
> > ---
> > drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
> > index e596e1a9fc75..236f244e3f65 100644
> > --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
> > +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
> > @@ -903,7 +903,9 @@ int ixgbe_ipsec_vf_add_sa(struct ixgbe_adapter *adapter, u32 *msgbuf, u32 vf)
> > /* Tx IPsec offload doesn't seem to work on this
> > * device, so block these requests for now.
> > */
> > - if (!(sam->flags & XFRM_OFFLOAD_INBOUND)) {
> > + sam->flags = sam->flags & ~XFRM_OFFLOAD_IPV6;
> > + if (!(sam->flags & XFRM_OFFLOAD_INBOUND) ||
> > + sam->flags & ~XFRM_OFFLOAD_INBOUND) {
>
> So after stripping the IPV6 flag, you're checking to be sure that INBOUND is
> the only flag enabled, right?
> Could you use
> if (sam->flags != XFRM_OFFLOAD_INBOUND) {
> instead?
Sure, I'll send new version soon.
Thanks
>
> sln
>
> > err = -EOPNOTSUPP;
> > goto err_out;
> > }
>
prev parent reply other threads:[~2022-03-31 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 11:01 [PATCH net] ixgbe: ensure IPsec VF<->PF compatibility Leon Romanovsky
2022-03-30 16:13 ` Shannon Nelson
2022-03-31 7:45 ` Leon Romanovsky [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=YkVcBgac41VjNBd7@unreal \
--to=leon@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=shannon.nelson@oracle.com \
--cc=snelson@pensando.io \
--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).