netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [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 15:02:38 -0700	[thread overview]
Message-ID: <20251015150238.6849de11@hermes.local> (raw)



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

Log from kernel dmesg is attached. 

Steps to Reproduce in a Libvirt/QEMU VM:
1) Install ArchLinux (all dependencies are available). I recommend using
archinstall, but anything can go
2) Install LXC/Incus (pacman -S incus)
3) configure incus for running: usermod -v 1000000-1000999999 -w
1000000-1000999999 root &&
incus admin init &&
incus launch images:debian/12 first
4) Previous step should trigger incus to do namespaces. I'm not sure what
syscall is causing the bug, so I do not have a mini C program. This should be
enough to see the log in the dmesg. (it can be done on any OS, VM is not
needed, but it was easier for me)


I also did a git bisect on the kernel, the first commit to have the bug is
0c17270f9b920e4e1777488f1911bbfdaf2af3be

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2025-10-15 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 22:02 Stephen Hemminger [this message]
2025-10-16  0:07 ` [Bug 220649] New: A bug is happening at __dev_change_net_namespace when runnning LXC/Incus service in 6.17 Jakub Kicinski

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=20251015150238.6849de11@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).