From: Simon Horman <horms@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: yogeshgaur.83@gmail.com, david@ixit.cz, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
ian.ray@gehealthcare.com, oe-linux-nfc@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+ebbbf06f152da8ea4716@syzkaller.appspotmail.com
Subject: Re: [PATCH] nfc: nci: drain rx_wq before cmd_wq on unregister
Date: Fri, 23 Oct 2026 16:07:45 +0100 [thread overview]
Message-ID: <20261023150745.GM708417@horms.kernel.org> (raw)
In-Reply-To: <179146631693.434549.10968955013781183787@kernel.org>
On Thu, Oct 08, 2026 at 01:31:56PM +0000, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential
> issue(s) to consider.
>
> Critical: 0 · High: 2 (1) · Medium: 0 · Low: 0
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [High] The new teardown order in nci_unregister_device() does not cover
> a deferred producer of tx_work: the NCI-HCI msg_rx_work, which runs on…
> - [High] nci_recv_frame() (net/nfc/nci/core.c:1360-1368) tests
> NCI_UP/NCI_INIT without a lock, then calls skb_queue_tail(&ndev->rx_q)…
I believe above issues are also pre-existing.
>
> Pre-existing issues:
> - [High] This problem was not introduced by this patch, but
> nxp_nci_i2c_remove() calls nxp_nci_remove() before…
There is always more to be done.
But this patch looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-10-23 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:28 Yogesh Gaur
2026-10-08 13:31 ` netdev-bot+sashiko
2026-10-23 15:07 ` Simon Horman [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=20261023150745.GM708417@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=edumazet@kernel.org \
--cc=ian.ray@gehealthcare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=syzbot+ebbbf06f152da8ea4716@syzkaller.appspotmail.com \
--cc=yogeshgaur.83@gmail.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
all inboxes | Powered by JetHome®