From: Jonas Theisen <j.theisen@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container 1/2] pct: Remove experimental state from mknod
Date: Fri, 2 Oct 2026 12:36:26 +0200 [thread overview]
Message-ID: <20261002103653.96619-1-j.theisen@proxmox.com> (raw)
Remove the experimental warning on the mknod option.
As discussed off-list this feature is considered stable.
Signed-off-by: Jonas Theisen <j.theisen@proxmox.com>
---
src/PVE/LXC/Config.pm | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
index 3eb1905..5c6804b 100644
--- a/src/PVE/LXC/Config.pm
+++ b/src/PVE/LXC/Config.pm
@@ -498,8 +498,7 @@ my $features_desc = {
default => 0,
description =>
"Allow unprivileged containers to use mknod() to add certain device nodes."
- . " This requires a kernel with seccomp trap to user space support (5.3 or newer)."
- . " This is experimental.",
+ . " This requires a kernel with seccomp trap to user space support (5.3 or newer).",
},
force_rw_sys => {
optional => 1,
--
2.47.3
next reply other threads:[~2026-10-02 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 10:36 Jonas Theisen [this message]
2026-10-02 10:36 ` [PATCH manager 2/2] lxc: features: Remove Experimental suffix from Device Nodes option Jonas Theisen
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=20261002103653.96619-1-j.theisen@proxmox.com \
--to=j.theisen@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 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.