From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-can@vger.kernel.org,
Network Development <netdev@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [can/j1939] unregister_netdevice: waiting for vcan0 to become free. Usage count = 2
Date: Fri, 21 Nov 2025 11:00:04 +0100 [thread overview]
Message-ID: <aSA4JMyFNdliTpli@pengutronix.de> (raw)
In-Reply-To: <3679c610-5795-4ddf-81ad-a9a043bab3fc@I-love.SAKURA.ne.jp>
On Fri, Nov 21, 2025 at 06:33:02PM +0900, Tetsuo Handa wrote:
> On 2025/11/21 18:06, Oleksij Rempel wrote:
> > Hm, looks like we have a race where new session is created in
> > j1939_xtp_rx_rts(), just at the moment where we call
> > j1939_can_rx_unregister().
> >
> > Haw about following change:
> >
> > --- a/net/can/j1939/main.c
> > +++ b/net/can/j1939/main.c
> > @@ -214,6 +214,7 @@ static void __j1939_rx_release(struct kref *kref)
> > rx_kref);
> >
> > j1939_can_rx_unregister(priv);
> > + j1939_cancel_active_session(priv, NULL);
> > j1939_ecu_unmap_all(priv);
> > j1939_priv_set(priv->ndev, NULL);
> > mutex_unlock(&j1939_netdev_lock);
> >
>
> Well, j1939_cancel_active_session(priv, NULL) is already called from
> j1939_netdev_notify(NETDEV_UNREGISTER). Unless a session is recreated
> after NETDEV_UNREGISTER event was handled, I can't imagine such race.
>
> We can see that there are three j1939_session_new() calls but only
> two j1939_session_destroy() calls. There might be a refcount leak on
> j1939_session which prevents j1939_priv from dropping final refcount.
>
> Call trace for vcan0@ffff888031c9c000 +2 at
> j1939_session_new+0x127/0x450 net/can/j1939/transport.c:1503
> j1939_tp_send+0x338/0x8c0 net/can/j1939/transport.c:2018
>
> Call trace for vcan0@ffff888031c9c000 +1 at
> j1939_session_new+0x127/0x450 net/can/j1939/transport.c:1503
> j1939_session_fresh_new net/can/j1939/transport.c:1543 [inline]
> j1939_xtp_rx_rts_session_new net/can/j1939/transport.c:1628 [inline]
> j1939_xtp_rx_rts+0xd16/0x18b0 net/can/j1939/transport.c:1749
>
> Call trace for vcan0@ffff888031c9c000 -2 at
> j1939_priv_put+0x23/0x370 net/can/j1939/main.c:184
> j1939_session_destroy net/can/j1939/transport.c:285 [inline]
> __j1939_session_release net/can/j1939/transport.c:294 [inline]
> kref_put include/linux/kref.h:65 [inline]
>
> Do we want to update
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/net/can/j1939?id=5ac798f79b48065b0284216c7a0057271185a882
> in order to also try tracing refcount for j1939_session ?
Ack.
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-11-21 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:11 [can/j1939] unregister_netdevice: waiting for vcan0 to become free. Usage count = 2 Tetsuo Handa
2025-11-21 9:06 ` Oleksij Rempel
2025-11-21 9:33 ` Tetsuo Handa
2025-11-21 10:00 ` Oleksij Rempel [this message]
2025-11-21 10:19 ` Tetsuo Handa
2025-11-21 10:31 ` Oleksij Rempel
2025-11-22 7:00 ` Tetsuo Handa
2025-11-22 13:03 ` Tetsuo Handa
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=aSA4JMyFNdliTpli@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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).