From: patchwork-bot+netdevbpf@kernel.org
To: Fan Wu <fanwu01@zju.edu.cn>
Cc: linux-can@vger.kernel.org, frank.jungclaus@esd.eu,
socketcan@esd.eu, mkl@pengutronix.de, mailhol@kernel.org,
jedrzej.jagielski@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] can: esd_usb: kill anchored URBs before freeing netdevs
Date: Fri, 17 Jul 2026 09:50:37 +0000 [thread overview]
Message-ID: <178428183738.1639384.11588765728790272276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260709164159.497640-1-fanwu01@zju.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Thu, 9 Jul 2026 16:41:59 +0000 you wrote:
> esd_usb_disconnect() frees each CAN netdev with free_candev() inside
> its per-netdev loop and only calls unlink_all_urbs(dev) afterwards.
> The per-netdev private data (struct esd_usb_net_priv) is embedded in
> the net_device allocation returned by alloc_candev(), so once
> free_candev() has run, dev->nets[i] points to freed memory.
> unlink_all_urbs() then dereferences the freed dev->nets[i] to kill the
> per-netdev TX anchor (usb_kill_anchored_urbs(&priv->tx_submitted)),
> clear active_tx_jobs, and reset priv->tx_contexts[].
>
> [...]
Here is the summary with links:
- [net,v2] can: esd_usb: kill anchored URBs before freeing netdevs
https://git.kernel.org/netdev/net/c/c43122fef328
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-07-17 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 10:46 [PATCH net] can: esd_usb: kill anchored URBs before freeing netdevs Fan Wu
2026-07-09 15:17 ` Jagielski, Jedrzej
2026-07-09 16:41 ` [PATCH net v2] " Fan Wu
2026-07-10 16:43 ` sashiko-bot
2026-07-17 9:50 ` patchwork-bot+netdevbpf [this message]
2026-07-10 10:47 ` [PATCH net] " sashiko-bot
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=178428183738.1639384.11588765728790272276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=fanwu01@zju.edu.cn \
--cc=frank.jungclaus@esd.eu \
--cc=jedrzej.jagielski@intel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@esd.eu \
--cc=stable@vger.kernel.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