From: "Michael Köppl" <m.koeppl@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Filip Schauer <f.schauer@proxmox.com>
Subject: Re: [pve-devel] [PATCH container v2 2/4] extract passthrough device node creation to a helper
Date: Fri, 30 May 2025 16:18:22 +0200 [thread overview]
Message-ID: <6d6c248b-0832-4e2e-afe9-3716586adb8b@proxmox.com> (raw)
In-Reply-To: <20250423125640.88756-3-f.schauer@proxmox.com>
On 4/23/25 14:56, Filip Schauer wrote:
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
> ---
> src/PVE/LXC.pm | 29 +++++++++++++++++++++++++++++
> src/lxc-pve-prestart-hook | 21 +--------------------
> 2 files changed, 30 insertions(+), 20 deletions(-)
>
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index d929608..d985b88 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -6,6 +6,7 @@ use warnings;
> use Cwd qw();
> use Errno qw(ELOOP ENOTDIR EROFS ECONNREFUSED EEXIST);
> use Fcntl qw(O_RDONLY O_WRONLY O_NOFOLLOW O_DIRECTORY :mode);
> +use File::Basename;
> use File::Path;
> use File::Spec;
> use IO::Poll qw(POLLIN POLLHUP);
> @@ -1662,6 +1663,34 @@ sub run_with_loopdev {
> return $device;
> }
>
> +sub create_passthrough_device_node($$$$$) {
> + my ($passthrough_dir, $device, $mode, $rdev, $id_map) = @_;
> +
> + # Create the device node
nit: I think this comment is stating what is already obvious from the code
> + my $passthrough_device_path = $passthrough_dir . $device->{path};
> + File::Path::make_path(dirname($passthrough_device_path));
> + PVE::Tools::mknod($passthrough_device_path, $mode, $rdev)
> + or die("failed to mknod $passthrough_device_path: $!\n");
> +
> + # Use chmod because umask could mess with the access mode on mknod
> + my $passthrough_mode = 0660;
> + $passthrough_mode = oct($device->{mode}) if defined($device->{mode});
> + chmod $passthrough_mode, $passthrough_device_path
> + or die "failed to chmod $passthrough_mode $passthrough_device_path: $!\n";
> +
> + # Set uid and gid of the device node
nit: same for this comment
> + my $uid = 0;
> + my $gid = 0;
> + $uid = $device->{uid} if defined($device->{uid});
> + $gid = $device->{gid} if defined($device->{gid});
> + $uid = PVE::LXC::map_ct_uid_to_host($uid, $id_map);
> + $gid = PVE::LXC::map_ct_gid_to_host($gid, $id_map);
> + chown $uid, $gid, $passthrough_device_path
> + or die("failed to chown $uid:$gid $passthrough_device_path: $!\n");
> +
> + return $passthrough_device_path;
> +}
> +
> # In scalar mode: returns a file handle to the deepest directory node.
> # In list context: returns a list of:
> # * the deepest directory node
> diff --git a/src/lxc-pve-prestart-hook b/src/lxc-pve-prestart-hook
> index fdaead2..61dfb3b 100755
> --- a/src/lxc-pve-prestart-hook
> +++ b/src/lxc-pve-prestart-hook
> @@ -144,26 +144,7 @@ PVE::LXC::Tools::lxc_hook('pre-start', 'lxc', sub {
> die "Could not get mode or device ID of $absolute_path\n"
> if (!defined($mode) || !defined($rdev));
>
> - my $passthrough_device_path = $passthrough_dir . $absolute_path;
> - File::Path::make_path(dirname($passthrough_device_path));
> - PVE::Tools::mknod($passthrough_device_path, $mode, $rdev)
> - or die("failed to mknod $passthrough_device_path: $!\n");
> -
> - # Use chmod because umask could mess with the access mode on mknod
> - my $passthrough_mode = 0660;
> - $passthrough_mode = oct($device->{mode}) if defined($device->{mode});
> - chmod $passthrough_mode, $passthrough_device_path
> - or die "failed to chmod $passthrough_mode $passthrough_device_path: $!\n";
> -
> - # Set uid and gid of the device node
> - my $uid = 0;
> - my $gid = 0;
> - $uid = $device->{uid} if defined($device->{uid});
> - $gid = $device->{gid} if defined($device->{gid});
> - $uid = PVE::LXC::map_ct_uid_to_host($uid, $id_map);
> - $gid = PVE::LXC::map_ct_gid_to_host($gid, $id_map);
> - chown $uid, $gid, $passthrough_device_path
> - or die("failed to chown $uid:$gid $passthrough_device_path: $!\n");
> + PVE::LXC::create_passthrough_device_node($passthrough_dir, $device, $mode, $rdev, $id_map);
>
> push @$passthrough_devices, [$absolute_path, $mode, $rdev];
> };
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-05-30 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:56 [pve-devel] [PATCH container v2 0/4] implement device hotplug Filip Schauer
2025-04-23 12:56 ` [pve-devel] [PATCH container v2 1/4] extract apparmor profile & namespace switch to a helper Filip Schauer
2025-04-23 12:56 ` [pve-devel] [PATCH container v2 2/4] extract passthrough device node creation " Filip Schauer
2025-05-30 14:18 ` Michael Köppl [this message]
2025-04-23 12:56 ` [pve-devel] [PATCH container v2 3/4] config: support printing a device Filip Schauer
2025-04-23 12:56 ` [pve-devel] [PATCH container v2 4/4] implement device hotplug Filip Schauer
2025-05-30 14:18 ` Michael Köppl
2025-06-02 11:40 ` Filip Schauer
2025-06-02 13:36 ` [pve-devel] superseded: [PATCH container v2 0/4] " Filip Schauer
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=6d6c248b-0832-4e2e-afe9-3716586adb8b@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal