netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: [PATCH v2 net-next 0/2] ipv6: fix hangup on device removal
Date: Tue,  5 Nov 2024 19:23:49 +0100	[thread overview]
Message-ID: <cover.1730828007.git.pabeni@redhat.com> (raw)

This addresses the infamous unregister_netdevice splat in net selftests;
the actual fix is carried by the first patch, while the 2nd one
addresses a related problem in the relevant test that was patially
hiding the problem.

Targeting net-next as the issue is quite old and I feel a little lost
in the fib info/nh jungle.
---
v1 -> v2:
 - drop unintended whitespace change in patch 1/2

Paolo Abeni (2):
  ipv6: release nexthop on device removal
  selftests: net: really check for bg process completion

 net/ipv6/route.c                    | 6 +++---
 tools/testing/selftests/net/pmtu.sh | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-11-05 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 18:23 Paolo Abeni [this message]
2024-11-05 18:23 ` [PATCH v2 net-next 1/2] ipv6: release nexthop on device removal Paolo Abeni
2024-11-05 18:26   ` Eric Dumazet
2024-11-05 21:40   ` David Ahern
2024-11-06  9:11     ` Paolo Abeni
2024-11-05 18:23 ` [PATCH v2 net-next 2/2] selftests: net: really check for bg process completion Paolo Abeni
2024-11-05 21:40   ` David Ahern
2024-11-07  2:00 ` [PATCH v2 net-next 0/2] ipv6: fix hangup on device removal patchwork-bot+netdevbpf

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=cover.1730828007.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@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;
as well as URLs for NNTP newsgroup(s).