From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Fan Wu <fanwu01@zju.edu.cn>
Cc: linux-wpan@vger.kernel.org,
Stefan Schmidt <stefan@datenfreihafen.org>,
Alexander Aring <alex.aring@gmail.com>,
Varka Bhadram <varkab@cdac.in>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ieee802154: cc2520: fix RX tasklet use-after-free
Date: Tue, 11 Aug 2026 10:28:05 +0200 [thread overview]
Message-ID: <87ik5hoycq.fsf@bootlin.com> (raw)
In-Reply-To: <20260811010359.131381-3-fanwu01@zju.edu.cn> (Fan Wu's message of "Tue, 11 Aug 2026 01:03:59 +0000")
Hi,
On 11/08/2026 at 01:03:59 GMT, Fan Wu <fanwu01@zju.edu.cn> wrote:
> The FIFOP interrupt was requested before cc2520_register(), so a failed
> registration could still have let the FIFOP handler queue RX work.
Really? How? SRXON is only set in ->start(), which means radio is off
until the user asks for it, which can only happen after proper netdev
registration.
It feels like the rest of this commit is pure AI hallucination, so I'll
stop there.
Thanks,
Miquèl
next prev parent reply other threads:[~2026-08-11 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 1:03 [PATCH v3 0/2] cc2520: fix FIFOP work and RX tasklet use-after-free Fan Wu
2026-08-11 1:03 ` [PATCH v3 1/2] ieee802154: cc2520: fix FIFOP work use-after-free Fan Wu
2026-08-11 8:00 ` Miquel Raynal
2026-08-11 1:03 ` [PATCH v3 2/2] ieee802154: cc2520: fix RX tasklet use-after-free Fan Wu
2026-08-11 8:28 ` Miquel Raynal [this message]
2026-08-11 9:48 ` Fan Wu
2026-08-11 13:14 ` Miquel Raynal
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=87ik5hoycq.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fanwu01@zju.edu.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=varkab@cdac.in \
/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