Netdev List
 help / color / mirror / Atom feed
From: Petr Oros <poros@redhat.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@kernel.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Ivan Vecera <ivecera@redhat.com>, Jiri Pirko <jiri@resnulli.us>,
	Petr Oros <poros@redhat.com>
Subject: [PATCH iproute2-next 0/2] dpll: do not fail on interrupted dumps
Date: Tue, 10 Nov 2026 12:00:59 +0100	[thread overview]
Message-ID: <20261110110101.2155953-1-poros@redhat.com> (raw)

A dpll device or pin dump that races with a registration or an
unregistration ends today as a failed command with a part of the list
on the output. This series makes the tool behave the way ip does in the
same situation. The whole dump is printed and a warning on stderr says
that it may be inconsistent.

The handling is added to mnl_utils as a separate helper that a caller
has to ask for, so the other users of mnlu_gen_socket keep their
current behaviour and can be converted one by one later. The helper
only reports the interruption. Whether to repeat the dump or to warn
is left to the caller, and dpll warns.

Petr Oros (2):
  mnl_utils: add a dump helper for NLM_F_DUMP_INTR
  dpll: warn about interrupted dumps

 dpll/dpll.c         | 37 ++++++++++++++++++-----------
 include/mnl_utils.h |  5 ++++
 lib/mnl_utils.c     | 58 +++++++++++++++++++++++++++++++++++++++------
 3 files changed, 79 insertions(+), 21 deletions(-)

-- 
2.56.0


             reply	other threads:[~2026-11-10 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 11:00 Petr Oros [this message]
2026-11-10 11:01 ` [PATCH iproute2-next 1/2] mnl_utils: add a dump helper for NLM_F_DUMP_INTR Petr Oros
2026-11-18 22:58   ` David Ahern
2026-11-10 11:01 ` [PATCH iproute2-next 2/2] dpll: warn about interrupted dumps Petr Oros

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=20261110110101.2155953-1-poros@redhat.com \
    --to=poros@redhat.com \
    --cc=dsahern@kernel.org \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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