From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 0380C6180E for ; Mon, 28 Sep 2020 07:28:47 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E4A1429950 for ; Mon, 28 Sep 2020 07:28:16 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 72D1A29943 for ; Mon, 28 Sep 2020 07:28:16 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3A2184580A for ; Mon, 28 Sep 2020 07:28:16 +0200 (CEST) Date: Mon, 28 Sep 2020 07:28:08 +0200 (CEST) From: Dietmar Maurer To: Proxmox Backup Server development discussion , Dominik Csapak Message-ID: <992604326.574.1601270889274@webmail.proxmox.com> In-Reply-To: <20200925141327.25024-6-d.csapak@proxmox.com> References: <20200925141327.25024-1-d.csapak@proxmox.com> <20200925141327.25024-6-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.3-Rev22 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.074 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [PATCH proxmox-backup 02/10] server/worker_task: refactor locking of the task list X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2020 05:28:47 -0000 > +fn lock_task_list_files(exclusive: bool) -> Result { > + let backup_user = crate::backup::backup_user()?; > + > + let lock = if exclusive { > + open_file_locked(PROXMOX_BACKUP_TASK_LOCK_FN, std::time::Duration::new(10, 0))? > + } else { > + open_file_locked_shared(PROXMOX_BACKUP_TASK_LOCK_FN, std::time::Duration::new(10, 0))? > + }; > + nix::unistd::chown(PROXMOX_BACKUP_TASK_LOCK_FN, Some(backup_user.uid), Some(backup_user.gid))?; You should use fchown here on the open file handle. > + > + Ok(lock) > +} This starts to get clumsy. We have: pub fn open_file_locked_shared>(path: P, timeout: Duration) -> Result and pub fn open_file_locked>(path: P, timeout: Duration) -> Result and private: fn open_file_locked_impl>(path: P, timeout: Duration, exclusive: bool) -> Result But we want: pub fn open_file_locked>(path: P, timeout: Duration, exclusive: bool) -> Result ...