From: Jakub Kicinski <kuba@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [Bug 220649] New: A bug is happening at __dev_change_net_namespace when runnning LXC/Incus service in 6.17
Date: Wed, 15 Oct 2025 17:07:24 -0700 [thread overview]
Message-ID: <20251015170724.7bd269f5@kernel.org> (raw)
In-Reply-To: <20251015150238.6849de11@hermes.local>
On Wed, 15 Oct 2025 15:02:38 -0700 Stephen Hemminger wrote:
> Begin forwarded message:
>
> Date: Thu, 09 Oct 2025 13:08:57 +0000
> From: bugzilla-daemon@kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 220649] New: A bug is happening at __dev_change_net_namespace when runnning LXC/Incus service in 6.17
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=220649
>
> Bug ID: 220649
> Summary: A bug is happening at __dev_change_net_namespace when
> runnning LXC/Incus service in 6.17
> Product: Networking
> Version: 2.5
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: kosmx.mc@gmail.com
> Regression: No
>
> Created attachment 308780
> --> https://bugzilla.kernel.org/attachment.cgi?id=308780&action=edit
> Archive containing the dmesg slice with stack trace, and the git bisect log
To avoid splintering discussion - this duplicates:
https://lore.kernel.org/all/01070199e22de7f8-28f711ab-d3f1-46d9-b9a0-048ab05eb09b-000000@eu-central-1.amazonses.com/
prev parent reply other threads:[~2025-10-16 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 22:02 Fw: [Bug 220649] New: A bug is happening at __dev_change_net_namespace when runnning LXC/Incus service in 6.17 Stephen Hemminger
2025-10-16 0:07 ` Jakub Kicinski [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=20251015170724.7bd269f5@kernel.org \
--to=kuba@kernel.org \
--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 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.