From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Jacob Keller" <jacob.e.keller@intel.com>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bpf@vger.kernel.org>, <magnus.karlsson@intel.com>,
Michal Kubiak <michal.kubiak@intel.com>,
Wojciech Drewek <wojciech.drewek@intel.com>,
Amritha Nambiar <amritha.nambiar@intel.com>
Subject: Re: [PATCH iwl-net v2 5/6] ice: remove ICE_CFG_BUSY locking from AF_XDP code
Date: Tue, 13 Aug 2024 12:28:15 +0200 [thread overview]
Message-ID: <Zrs1P/2ZtVsKhd+6@boxer> (raw)
In-Reply-To: <ZroxWcFbhF2KSKeb@lzaremba-mobl.ger.corp.intel.com>
On Mon, Aug 12, 2024 at 05:59:21PM +0200, Larysa Zaremba wrote:
> On Mon, Aug 12, 2024 at 03:03:19PM +0200, Maciej Fijalkowski wrote:
> > On Wed, Jul 24, 2024 at 06:48:36PM +0200, Larysa Zaremba wrote:
> > > Locking used in ice_qp_ena() and ice_qp_dis() does pretty much nothing,
> > > because ICE_CFG_BUSY is a state flag that is supposed to be set in a PF
> > > state, not VSI one. Therefore it does not protect the queue pair from
> > > e.g. reset.
> > >
> > > Despite being useless, it still can deadlock the unfortunate functions that
> > > have fell into the same ICE_CFG_BUSY-VSI trap. This happens if ice_qp_ena
> > > returns an error.
> > >
> > > Remove ICE_CFG_BUSY locking from ice_qp_dis() and ice_qp_ena().
> >
> > Why not just check the pf->state ?
>
> I would just cite Jakub: "you lose lockdep and all other infra normal mutex
> would give you." [0]
I was not sure why you're bringing up mutex here but I missed 2nd patch
somehow :) let me start from the beginning.
>
> [0] https://lore.kernel.org/netdev/20240612140935.54981c49@kernel.org/
>
> > And address other broken callsites?
>
> Because the current state of sychronization does not allow me to assume this
> would fix anything and testing all the places would be out of scope for theese
> series.
>
> With Dawid's patch [1], a mutex for XDP and miscellaneous changes from these
> series I think we would probably come pretty close being able to get rid of
> ICE_CFG_BUSY at least when locking software resources.
>
> [1]
> https://lore.kernel.org/netdev/20240812125009.62635-1-dawid.osuchowski@linux.intel.com/
>
> > >
> > > Fixes: 2d4238f55697 ("ice: Add support for AF_XDP")
> > > Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> > > Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
> > > ---
> > > drivers/net/ethernet/intel/ice/ice_xsk.c | 9 ---------
> > > 1 file changed, 9 deletions(-)
> > >
> > > diff --git a/drivers/net/ethernet/intel/ice/ice_xsk.c b/drivers/net/ethernet/intel/ice/ice_xsk.c
> > > index 5dd50a2866cc..d23fd4ea9129 100644
> > > --- a/drivers/net/ethernet/intel/ice/ice_xsk.c
> > > +++ b/drivers/net/ethernet/intel/ice/ice_xsk.c
> > > @@ -163,7 +163,6 @@ static int ice_qp_dis(struct ice_vsi *vsi, u16 q_idx)
> > > struct ice_q_vector *q_vector;
> > > struct ice_tx_ring *tx_ring;
> > > struct ice_rx_ring *rx_ring;
> > > - int timeout = 50;
> > > int err;
> > >
> > > if (q_idx >= vsi->num_rxq || q_idx >= vsi->num_txq)
> > > @@ -173,13 +172,6 @@ static int ice_qp_dis(struct ice_vsi *vsi, u16 q_idx)
> > > rx_ring = vsi->rx_rings[q_idx];
> > > q_vector = rx_ring->q_vector;
> > >
> > > - while (test_and_set_bit(ICE_CFG_BUSY, vsi->state)) {
> > > - timeout--;
> > > - if (!timeout)
> > > - return -EBUSY;
> > > - usleep_range(1000, 2000);
> > > - }
> > > -
> > > ice_qvec_dis_irq(vsi, rx_ring, q_vector);
> > > ice_qvec_toggle_napi(vsi, q_vector, false);
> > >
> > > @@ -250,7 +242,6 @@ static int ice_qp_ena(struct ice_vsi *vsi, u16 q_idx)
> > > ice_qvec_ena_irq(vsi, q_vector);
> > >
> > > netif_tx_start_queue(netdev_get_tx_queue(vsi->netdev, q_idx));
> > > - clear_bit(ICE_CFG_BUSY, vsi->state);
> > >
> > > return 0;
> > > }
> > > --
> > > 2.43.0
> > >
next prev parent reply other threads:[~2024-08-13 10:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 16:48 [PATCH iwl-net v2 0/6] ice: fix synchronization between .ndo_bpf() and reset Larysa Zaremba
2024-07-24 16:48 ` [PATCH iwl-net v2 1/6] ice: move netif_queue_set_napi to rtnl-protected sections Larysa Zaremba
2024-07-24 18:21 ` Jacob Keller
2024-07-24 20:40 ` Nambiar, Amritha
2024-08-08 2:19 ` [Intel-wired-lan] " Rout, ChandanX
2024-07-24 16:48 ` [PATCH iwl-net v2 2/6] ice: protect XDP configuration with a mutex Larysa Zaremba
2024-07-24 18:24 ` Jacob Keller
2024-08-08 2:16 ` [Intel-wired-lan] " Rout, ChandanX
2024-08-13 11:31 ` Maciej Fijalkowski
2024-08-13 13:36 ` Larysa Zaremba
2024-07-24 16:48 ` [PATCH iwl-net v2 3/6] ice: check for XDP rings instead of bpf program when unconfiguring Larysa Zaremba
2024-07-24 18:25 ` Jacob Keller
2024-08-08 2:18 ` [Intel-wired-lan] " Rout, ChandanX
2024-08-12 12:58 ` Maciej Fijalkowski
2024-08-12 15:13 ` Larysa Zaremba
2024-07-24 16:48 ` [PATCH iwl-net v2 4/6] ice: check ICE_VSI_DOWN under rtnl_lock when preparing for reset Larysa Zaremba
2024-07-24 18:27 ` Jacob Keller
2024-08-08 2:15 ` [Intel-wired-lan] " Rout, ChandanX
2024-07-24 16:48 ` [PATCH iwl-net v2 5/6] ice: remove ICE_CFG_BUSY locking from AF_XDP code Larysa Zaremba
2024-07-24 18:37 ` Jacob Keller
2024-08-08 2:17 ` [Intel-wired-lan] " Rout, ChandanX
2024-08-12 13:03 ` Maciej Fijalkowski
2024-08-12 15:59 ` Larysa Zaremba
2024-08-13 10:28 ` Maciej Fijalkowski [this message]
2024-07-24 16:48 ` [PATCH iwl-net v2 6/6] ice: do not bring the VSI up, if it was down before the XDP setup Larysa Zaremba
2024-07-24 18:40 ` Jacob Keller
2024-08-08 2:14 ` [Intel-wired-lan] " Rout, ChandanX
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=Zrs1P/2ZtVsKhd+6@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wojciech.drewek@intel.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).