From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219190] New: Kernel USB device namespacing
Date: Thu, 22 Aug 2024 10:19:25 +0000 [thread overview]
Message-ID: <bug-219190-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219190
Bug ID: 219190
Summary: Kernel USB device namespacing
Product: Virtualization
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: weiss_julian@outlook.de
Regression: No
When trying to bring a Rpi Compute Module 4 into flashable state. One has to
connect the CM4 via USB to e.g. another Linux PC and exeecute rpiboot. Rpiboot
will probe for the correct USB device, writes something to it, makes the device
reconnect the USB connection and writes to the device again.
When executing the rpiboot tool from within a podman container, which is
started in privileged mode, rpiboot will successful probe the device and
execute the first write. However, after resetting the device, strace shows
rpiboot is about to open an USB device, which does not exist inside the
container. When checking the hosts filesystem, the USB device exists at that
specific location.
How is it possible that my container knows the correct location of the outsides
USB device, but is unable to find the filename of the USB device inside the
container?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2024-08-22 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-219190-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@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