From: Jakub Kicinski <kuba@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Network Development <netdev@vger.kernel.org>
Subject: Re: Can networking trees carry temporary patches?
Date: Wed, 25 Mar 2026 19:22:14 -0700 [thread overview]
Message-ID: <20260325192214.133ffaaf@kernel.org> (raw)
In-Reply-To: <e0c7030b-261c-4ed1-b6b0-bf3b83a41d60@I-love.SAKURA.ne.jp>
On Tue, 24 Mar 2026 19:55:18 +0900 Tetsuo Handa wrote:
> I was carrying debug printk() patches [1][2] in linux-next tree via my tree
> in order to debug "unregister_netdevice: waiting for DEV to become free"
> problem [3].
>
> While these patches had been a lot helpful, now that easily reproducible cases
> has been fixed, this problem is hardly reproduced in linux-next tree recently;
> giving me no hints for debugging remaining cases. However, this problem is still
> reproduced in networking trees.
>
> Therefore, I appreciate if networking trees can carry temporary patches
> (patches which are not intended to be merged into the linux.git tree).
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit?id=58b4f8f612187b0d9583b5549044734ecd7071eb
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit?id=02fb7fbf5db47bf5c1736b692888232f5f6bf80e
> [3] https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
Have you see netdev_hold() / netdev_put() ?
next prev parent reply other threads:[~2026-03-26 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 10:55 Can networking trees carry temporary patches? Tetsuo Handa
2026-03-26 2:22 ` Jakub Kicinski [this message]
2026-03-26 3:32 ` 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=20260325192214.133ffaaf@kernel.org \
--to=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.