From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id F14E31FF170 for ; Thu, 7 Aug 2025 16:53:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8478B32142; Thu, 7 Aug 2025 16:55:14 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Shannon Sterz Date: Thu, 7 Aug 2025 16:54:55 +0200 Message-ID: <175457836714.113987.193439260852613390.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250807142246.341381-1-s.sterz@proxmox.com> References: <20250807142246.341381-1-s.sterz@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754578488714 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.024 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH manager v2] 8 to 9: use check for unified cgroup v2 support via pve-container X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu, 07 Aug 2025 16:22:46 +0200, Shannon Sterz wrote: > ...instead of re-implementing a custom check here. This has the > side-effect that the check implemented by pve-container is much more > robust and is less likely to yield false positive. So users won't get > warnings about containers that actually do have the required unified > cgroup v2 support. > > This was reported for an OpenSUSE Slowroll container on the forum: > https://forum.proxmox.com/threads/169302/ > > [...] Applied, thanks! Made a separate commit running 'make tidy' first and rebased on top of that to get a clean change. [1/1] 8 to 9: use check for unified cgroup v2 support via pve-container commit: ea1f2523515d7639f754a0588ffd8800cdb3321f and for stable-8: [1/1] 8 to 9: use check for unified cgroup v2 support via pve-container commit: 24cd98ac41e83efd3c235cd50e47c66429bb106b _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel