All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC PATCH net-next 0/1] cxgb4: fix missing unlock on ETHOFLD desc collect fail path
@ 2022-09-22  5:32 Rafael Mendonca
  2022-09-22  5:32 ` [RFC PATCH net-next 1/1] " Rafael Mendonca
  0 siblings, 1 reply; 3+ messages in thread
From: Rafael Mendonca @ 2022-09-22  5:32 UTC (permalink / raw)
  To: Raju Rangoju, David S. Miller, Eric Dumazet, Jakub Kicinski,
	Paolo Abeni, Rahul Lakkireddy
  Cc: Rafael Mendonca, netdev, linux-kernel

I'm sending this as a RFC because I'm not familiar with the chelsio
cxgb4 code, sorry if this is nonsense.

I noticed that the 'out' label is passed to the QDESC_GET for the
ETHOFLD TXQ, RXQ, and FLQ, which skips the 'out_unlock' label on error,
and thus doesn't unlock the 'uld_mutex' before returning.

I was thinking the solution would be to simply change the label to
'out_unlock'. However, since commit 5148e5950c67 ("cxgb4: add EOTID
tracking and software context dump"), I was wondering if the access to
these ETHOFLD hardware queues should be protected by the 'mqprio_mutex'
instead of the 'uld_mutex'.

Rafael Mendonca (1):
  cxgb4: fix missing unlock on ETHOFLD desc collect fail path

 .../net/ethernet/chelsio/cxgb4/cudbg_lib.c    | 28 +++++++++++++------
 1 file changed, 19 insertions(+), 9 deletions(-)

-- 
2.34.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-22 10:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-22  5:32 [RFC PATCH net-next 0/1] cxgb4: fix missing unlock on ETHOFLD desc collect fail path Rafael Mendonca
2022-09-22  5:32 ` [RFC PATCH net-next 1/1] " Rafael Mendonca
2022-09-22  9:21   ` Rahul Lakkireddy

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.