All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next] netconsole: clear cached dev_name on resume-window cleanup
Date: Sat, 13 Jun 2026 01:00:30 +0000	[thread overview]
Message-ID: <178131243063.1315131.4483049658366327192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610-netconsole_fix_more-v1-1-a18652c47cef@debian.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 10 Jun 2026 07:26:04 -0700 you wrote:
> When process_resume_target() catches a device that was unregistered
> while the target was off target_list, it calls do_netpoll_cleanup() to
> release the reference but leaves the cached np.dev_name in place. The
> other cleanup path, netconsole_process_cleanups_core(), already wipes
> dev_name for MAC-bound targets because the name was only a cache of the
> device that last carried the MAC and may no longer match.
> 
> [...]

Here is the summary with links:
  - [net-next] netconsole: clear cached dev_name on resume-window cleanup
    https://git.kernel.org/netdev/net-next/c/02a61d2018c4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-13  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 14:26 [PATCH net-next] netconsole: clear cached dev_name on resume-window cleanup Breno Leitao
2026-06-10 20:14 ` Andre Carvalho
2026-06-13  1:00 ` patchwork-bot+netdevbpf [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=178131243063.1315131.4483049658366327192.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.