mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jiale Yao <yaojiale02@163.com>
Cc: "Théo Lebrun" <theo.lebrun@bootlin.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>, "Wei Fang" <wei.fang@nxp.com>,
	"Frank Li" <frank.li@nxp.com>,
	"Shenwei Wang" <shenwei.wang@nxp.com>,
	"Jian Shen" <shenjian15@huawei.com>,
	"Jijie Shao" <shaojijie@huawei.com>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Paul Barker" <paul@pbarker.dev>,
	"Byungho An" <bh74.an@samsung.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Soren Brinkmann" <soren.brinkmann@xilinx.com>,
	"Fabio Estevam" <fabio.estevam@freescale.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Zhangfei Gao" <zhangfei.gao@linaro.org>,
	dingtianhong <dingtianhong@huawei.com>,
	"Jiancheng Xue" <xuejiancheng@hisilicon.com>,
	"Dongpo Li" <lidongpo@hisilicon.com>,
	"Mitsuhiro Kimura" <mitsuhiro.kimura.kc@renesas.com>,
	"Sergei Shtylyov" <sergei.shtylyov@cogentembedded.com>,
	"Sergey Shtylyov" <s.shtylyov@omp.ru>,
	"Claudiu Beznea" <claudiu.beznea.uj@bp.renesas.com>,
	"Vipul Pandya" <vipul.pandya@samsung.com>,
	"Girish K S" <ks.giri@samsung.com>,
	"Siva Reddy" <siva.kallam@samsung.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/7] net: ethernet: release managed IRQs before freeing netdevs
Date: Sun, 27 Sep 2026 15:30:20 -0700	[thread overview]
Message-ID: <20260927153020.5311dba6@kernel.org> (raw)
In-Reply-To: <20260927144741.1320558-1-yaojiale02@163.com>

On Sun, 27 Sep 2026 22:47:33 +0800 Jiale Yao wrote:
> Several Ethernet platform drivers request interrupts with
> devm_request_irq() but allocate and free their netdevs manually.
> Device-managed resources are released only after the driver's remove
> callback returns, so these callbacks free the IRQ data while the interrupt
> handlers can still be invoked. A late or shared interrupt in this window
> can dereference freed memory.

This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:

 - How the issue was discovered, e.g. hit in production, hit during
   development, syzbot report, manual code inspection, LLM or static
   analysis tool scan.

 - Whether the issue was actually triggered, or is only theoretical
   (e.g. found by code inspection). If it was triggered please include
   the symptoms, like the stack trace or error messages.

 - What hardware the change was tested on. For driver fixes please
   mention the device (and if relevant firmware version) used for
   testing, or say that the change was not tested on real hardware.

Please do not repost the series just to address the above. Instead,
reply to this email with the missing information, so that reviewers
can take it into account. If the series needs another revision for
other reasons, please include the information in the commit messages
then.

      parent reply	other threads:[~2026-09-27 22:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 14:47 Jiale Yao
2026-09-27 14:47 ` [PATCH v2 1/7] net: macb: manage the netdev lifetime with devres Jiale Yao
2026-09-27 14:47 ` [PATCH v2 2/7] net: fec: " Jiale Yao
2026-09-28  2:57   ` Wei Fang
2026-09-27 14:47 ` [PATCH v2 3/7] net: hip04: " Jiale Yao
2026-09-30  3:48   ` netdev-bot+sashiko
2026-09-27 14:47 ` [PATCH v2 4/7] net: hisi_femac: " Jiale Yao
2026-09-27 14:47 ` [PATCH v2 5/7] net: hix5hd2: " Jiale Yao
2026-09-27 14:47 ` [PATCH v2 6/7] net: ravb: fix resource teardown ordering Jiale Yao
2026-09-27 16:01   ` Niklas Söderlund
2026-09-28  9:33     ` jiale yao
2026-09-29 19:07   ` Sergey Shtylyov
2026-09-30  1:53     ` jiale yao
2026-09-30  3:49   ` netdev-bot+sashiko
2026-09-27 14:47 ` [PATCH v2 7/7] net: sxgbe: manage IRQ data lifetimes with devres Jiale Yao
2026-09-30  3:49   ` netdev-bot+sashiko
2026-09-27 22:30 ` Jakub Kicinski [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=20260927153020.5311dba6@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=bh74.an@samsung.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=dingtianhong@huawei.com \
    --cc=edumazet@google.com \
    --cc=fabio.estevam@freescale.com \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=ks.giri@samsung.com \
    --cc=lidongpo@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mitsuhiro.kimura.kc@renesas.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=pabeni@redhat.com \
    --cc=paul@pbarker.dev \
    --cc=s.shtylyov@omp.ru \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=shenwei.wang@nxp.com \
    --cc=siva.kallam@samsung.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=theo.lebrun@bootlin.com \
    --cc=vipul.pandya@samsung.com \
    --cc=wei.fang@nxp.com \
    --cc=xuejiancheng@hisilicon.com \
    --cc=yaojiale02@163.com \
    --cc=zhangfei.gao@linaro.org \
    /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®