From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id B81C81FF130 for ; Mon, 20 Jul 2026 16:12:33 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3E43B214AA; Mon, 20 Jul 2026 16:12:33 +0200 (CEST) Message-ID: <43945d83-ad3c-4988-9f27-83dac1577ca8@proxmox.com> Date: Mon, 20 Jul 2026 16:12:28 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH proxmox-backup v3 14/15] tape: use proxmox-product-config to generate create options To: Robert Obkircher , pbs-devel@lists.proxmox.com References: <20260701140412.200920-1-c.ebner@proxmox.com> <20260701140412.200920-15-c.ebner@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784556724820 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.402 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: MODW3T4P7LJ4TILYZLMEGMFMALILIJDB X-Message-ID-Hash: MODW3T4P7LJ4TILYZLMEGMFMALILIJDB X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 7/6/26 2:28 PM, Robert Obkircher wrote: > > On 01.07.26 16:05, Christian Ebner wrote: >> Instead of redefining them, use the global helper defined in >> proxmox-product-config. Requires the crates init function to be >> called exactly once before using in any callpath. >> >> Signed-off-by: Christian Ebner >> --- >> src/tape/inventory.rs | 6 +----- >> src/tape/media_catalog_cache.rs | 10 +--------- >> 2 files changed, 2 insertions(+), 14 deletions(-) >> >> diff --git a/src/tape/inventory.rs b/src/tape/inventory.rs >> index 6c54738fb..12cca02c6 100644 >> --- a/src/tape/inventory.rs >> +++ b/src/tape/inventory.rs >> @@ -177,11 +177,7 @@ impl Inventory { >> // We cannot use chown inside test environment (no permissions) >> CreateOptions::new().perm(mode) >> } else { >> - let backup_user = pbs_config::backup_user()?; >> - CreateOptions::new() >> - .perm(mode) >> - .owner(backup_user.uid) >> - .group(backup_user.gid) >> + proxmox_product_config::default_create_options() >> }; > I think the then branch of this if statement could be removed, because > for cfg!(test) the backup_user is already set to the current user. Thanks for the hint, at first glance it should behave as you expected but I can trigger test failures without that, getting an EPERM error on fchown on CreateOptions::apply_at(). I guess this is caused by (man 2 fchown): > Only a privileged process (Linux: one with the CAP_CHOWN capability) may change the owner of a file. Didn't investigate further though and opted for leaving the checks in place.