From: Salvatore Bonaccorso <carnil@debian.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Ben Hutchings <benh@debian.org>,
Roland Schwarzkopf <rschwarzkopf@mathematik.uni-marburg.de>,
Nikolay Aleksandrov <razor@blackwall.org>,
David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Sasha Levin <sashal@kernel.org>,
debian-kernel@lists.debian.org,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, regressions@lists.linux.dev,
1124549@bugs.debian.org
Subject: Re: [regression 5.10.y] Libvirt can no longer delete macvtap devices after backport of a6cec0bcd342 ("net: rtnetlink: add bulk delete support flag") to 5.10.y series (Debian 11)
Date: Mon, 5 Jan 2026 19:14:13 +0100 [thread overview]
Message-ID: <aVv_dewfbbgQ5o0J@eldamar.lan> (raw)
In-Reply-To: <6498cffd-5bf9-490a-910d-f64ab9b7f330@leemhuis.info>
Hi,
On Mon, Jan 05, 2026 at 01:30:59PM +0100, Thorsten Leemhuis wrote:
> @stable team and/or @net maintainers: this imho needs a judgement call
> from your side. See below for details.
>
> On 1/2/26 21:18, Ben Hutchings wrote:
> > On Fri, 2025-12-19 at 10:19 +0100, Thorsten Leemhuis wrote:
> >> On 12/18/25 20:50, Salvatore Bonaccorso wrote:
> >>>
> >>> Is there soemthing missing?
> >>>
> >>> Roland I think it would be helpful if you can test as well more recent
> >>> stable series versions to confirm if the issue is present there as
> >>> well or not, which might indicate a 5.10.y specific backporting
> >>> problem.
> >>
> >> FWIW, it (as usual) would be very important to know if this happens with
> >> mainline as well, as that determines if it's a general problem or a
> >> backporting problem
> > [...]
> >
> > The bug is this:
> >
> > - libvirtd wrongly used to use NLM_F_CREATE (0x400) and NLM_F_EXCL
> > (0x200) flags on an RTM_DELLINK operation. These flags are only
> > semantically valid for NEW-type operations.
> >
> > - rtnetlink is rather lax about checking the flags on operations, so
> > these unsupported flags had no effect.
> >
> > - rtnetlink can now support NLM_F_BULK (0x200) on some DEL-type
> > operations. If the flag is used but is not valid for the specific
> > operation then the operation now fails with EOPNOTSUPP. Since
> > NLM_F_EXCL == NLM_F_BULK and RTM_DELLINK does not support bulk
> > operations, libvirtd now hits this error case.
> >
> > I have not tested with mainline, but in principle the same issue should
> > occur with any other kernel version that has commit a6cec0bcd342 "net:
> > rtnetlink: add bulk delete support flag"
>
> FWIW, merged for v5.19-rc1 and backported to v5.10.246 as 1550f3673972c5
> End of October 2025 in parallel with 5b22f62724a0a0 ("net: rtnetlink:
> fix module reference count leak issue in rtnetlink_rcv_msg") [v6.0-rc2],
> which is a fix for the former.
>
> > together with an older version of libvirt.
> >
> > This was fixed in libvirt commit 1334002340b, which appears to have gone
> > into version 7.1.0,
>
> Could not find that commit when looking briefly, but that version was
> released 2021-03-01.
For reference it is this one I think:
https://gitlab.com/libvirt/libvirt/-/commit/81334002340be6bd3a1a34c6584a85fe25cc049c
Regards,
Salvatore
next prev parent reply other threads:[~2026-01-05 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0b06eb09-b1a9-41f9-8655-67397be72b22@mathematik.uni-marburg.de>
[not found] ` <aUMEVm1vb7bdhlcK@eldamar.lan>
[not found] ` <e8bcfe99-5522-4430-9826-ed013f529403@mathematik.uni-marburg.de>
2025-12-18 19:50 ` [regression 5.10.y] Libvirt can no longer delete macvtap devices after backport of a6cec0bcd342 ("net: rtnetlink: add bulk delete support flag") to 5.10.y series (Debian 11) Salvatore Bonaccorso
2025-12-19 9:19 ` Thorsten Leemhuis
2026-01-02 20:18 ` Ben Hutchings
2026-01-05 12:30 ` Thorsten Leemhuis
2026-01-05 18:14 ` Salvatore Bonaccorso [this message]
2025-12-19 17:14 ` Roland Schwarzkopf
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=aVv_dewfbbgQ5o0J@eldamar.lan \
--to=carnil@debian.org \
--cc=1124549@bugs.debian.org \
--cc=benh@debian.org \
--cc=davem@davemloft.net \
--cc=debian-kernel@lists.debian.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rschwarzkopf@mathematik.uni-marburg.de \
--cc=sashal@kernel.org \
--cc=stable@vger.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