From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Thomas Kopp" <thomas.kopp@microchip.com>,
"Vincent Mailhol" <mailhol.vincent@wanadoo.fr>,
<kernel@pengutronix.de>, "Heiko Stuebner" <heiko@sntech.de>,
"Chandrasekar Ramakrishnan" <rcsekar@samsung.com>
Cc: <linux-can@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 2/3] can: rockchip_canfd: m_can_class_unregister: fix order of unregistration calls
Date: Mon, 05 May 2025 09:58:23 +0200 [thread overview]
Message-ID: <D9O2FWGG83V6.L6IQOPRGZL68@baylibre.com> (raw)
In-Reply-To: <20250502-can-rx-offload-del-v1-2-59a9b131589d@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
On Fri May 2, 2025 at 4:13 PM CEST, Marc Kleine-Budde wrote:
> If a driver is removed, the driver framework invokes the driver's
> remove callback. A CAN driver's remove function calls
> unregister_candev(), which calls net_device_ops::ndo_stop further down
> in the call stack for interfaces which are in the "up" state.
>
> The removal of the module causes the a warning, as
^^^
Minor typo here.
Otherwise this looks good to me.
Reviewed-by: Markus Schneider-Pargmann
> can_rx_offload_del() deletes the NAPI, while it is still active,
> because the interface is still up.
>
> To fix the warning, first unregister the network interface, which
> calls net_device_ops::ndo_stop, which disables the NAPI, and then call
> can_rx_offload_del().
>
> Fixes: ff60bfbaf67f ("can: rockchip_canfd: add driver for Rockchip CAN-FD controller")
> Cc: stable@vger.kernel.org
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> drivers/net/can/rockchip/rockchip_canfd-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/rockchip/rockchip_canfd-core.c b/drivers/net/can/rockchip/rockchip_canfd-core.c
> index 7107a37da36c..c3fb3176ce42 100644
> --- a/drivers/net/can/rockchip/rockchip_canfd-core.c
> +++ b/drivers/net/can/rockchip/rockchip_canfd-core.c
> @@ -937,8 +937,8 @@ static void rkcanfd_remove(struct platform_device *pdev)
> struct rkcanfd_priv *priv = platform_get_drvdata(pdev);
> struct net_device *ndev = priv->ndev;
>
> - can_rx_offload_del(&priv->offload);
> rkcanfd_unregister(priv);
> + can_rx_offload_del(&priv->offload);
> free_candev(ndev);
> }
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2025-05-05 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 14:13 [PATCH 0/3] can: rx-offload: fix order of unregistration calls Marc Kleine-Budde
2025-05-02 14:13 ` [PATCH 1/3] can: mcp251xfd: mcp251xfd_remove(): " Marc Kleine-Budde
2025-05-02 14:13 ` [PATCH 2/3] can: rockchip_canfd: m_can_class_unregister: " Marc Kleine-Budde
2025-05-05 7:58 ` Markus Schneider-Pargmann [this message]
2025-05-02 14:13 ` [PATCH 3/3] can: mcan: " Marc Kleine-Budde
2025-05-05 8:01 ` Markus Schneider-Pargmann
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=D9O2FWGG83V6.L6IQOPRGZL68@baylibre.com \
--to=msp@baylibre.com \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mkl@pengutronix.de \
--cc=rcsekar@samsung.com \
--cc=stable@vger.kernel.org \
--cc=thomas.kopp@microchip.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;
as well as URLs for NNTP newsgroup(s).