From: Ian Ray <ian.ray@gehealthcare.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
ilane@ti.com, linville@tuxdriver.com
Subject: Re: [PATCH net] nfc: nci: fix circular locking dependency in nci_close_device
Date: Wed, 18 Mar 2026 17:04:28 +0200 [thread overview]
Message-ID: <abq-_ATeXRYpVCEU@zeus> (raw)
In-Reply-To: <20260317193334.988609-1-kuba@kernel.org>
On Tue, Mar 17, 2026 at 12:33:34PM -0700, Jakub Kicinski wrote:
> nci_close_device() flushes rx_wq and tx_wq while holding req_lock.
> This causes a circular locking dependency because nci_rx_work()
> running on rx_wq can end up taking req_lock too:
>
> nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete
> -> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target
> -> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock)
>
> Move the flush of rx_wq after req_lock has been released.
> This should safe (I think) because NCI_UP has already been cleared
> and the transport is closed, so the work will see it and return
> -ENETDOWN.
>
> NIPA has been hitting this running the nci selftest with a debug
> kernel on roughly 4% of the runs.
>
> Fixes: 6a2968aaf50c ("NFC: basic NCI protocol implementation")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Ian Ray <ian.ray@gehealthcare.com>
> ---
> CC: ian.ray@gehealthcare.com
> CC: ilane@ti.com
> CC: linville@tuxdriver.com
> ---
> net/nfc/nci/core.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/net/nfc/nci/core.c b/net/nfc/nci/core.c
> index 43d871525dbc..5f46c4b5720f 100644
> --- a/net/nfc/nci/core.c
> +++ b/net/nfc/nci/core.c
> @@ -579,8 +579,7 @@ static int nci_close_device(struct nci_dev *ndev)
> skb_queue_purge(&ndev->rx_q);
> skb_queue_purge(&ndev->tx_q);
>
> - /* Flush RX and TX wq */
> - flush_workqueue(ndev->rx_wq);
> + /* Flush TX wq, RX wq flush can't be under the lock */
> flush_workqueue(ndev->tx_wq);
>
> /* Reset device */
> @@ -592,13 +591,13 @@ static int nci_close_device(struct nci_dev *ndev)
> msecs_to_jiffies(NCI_RESET_TIMEOUT));
>
> /* After this point our queues are empty
> - * and no works are scheduled.
> + * rx work may be running but will see that NCI_UP was cleared
> */
> ndev->ops->close(ndev);
>
> clear_bit(NCI_INIT, &ndev->flags);
>
> - /* Flush cmd wq */
> + /* Flush cmd and tx wq */
> flush_workqueue(ndev->cmd_wq);
>
> timer_delete_sync(&ndev->cmd_timer);
> @@ -613,6 +612,9 @@ static int nci_close_device(struct nci_dev *ndev)
>
> mutex_unlock(&ndev->req_lock);
>
> + /* rx_work may take req_lock via nci_deactivate_target */
> + flush_workqueue(ndev->rx_wq);
> +
> return 0;
> }
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-03-18 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 19:33 [PATCH net] nfc: nci: fix circular locking dependency in nci_close_device Jakub Kicinski
2026-03-18 15:04 ` Ian Ray [this message]
2026-03-20 0:00 ` patchwork-bot+netdevbpf
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=abq-_ATeXRYpVCEU@zeus \
--to=ian.ray@gehealthcare.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ilane@ti.com \
--cc=kuba@kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.