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 DCCC31FF0A8 for ; Sat, 14 Nov 2026 22:28:02 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id ACCF4215A1; Sat, 14 Nov 2026 22:28:00 +0100 (CET) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Jakob-Tobias Winter Subject: applied: [PATCH proxmox-backup v2] tape: virtual drive: fix endless recursion in changer status Date: Sat, 14 Nov 2026 22:27:44 +0100 Message-ID: <179469166100.2392541.4609096885465042611.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261111204853.531985-2-tobias@stuttgart.de> References: <20261111204853.531985-2-tobias@stuttgart.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794691673407 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.233 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_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 Message-ID-Hash: BSHXB2TISYCITU3DBWKTEKYF3FBVQ4IO X-Message-ID-Hash: BSHXB2TISYCITU3DBWKTEKYF3FBVQ4IO X-MailFrom: t.lamprecht@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 Wed, 11 Nov 2026 21:48:54 +0100, Jakob-Tobias Winter wrote: > The virtual tape drive, which exists for tests and debugging only, also > acts as its own changer and reports every virtual tape in its directory > as a slot. To build that status it asks for the list of online media. > The drive has its own way to get that list, the tapes in its directory, > but that was kept next to the changer interface instead of being part of > it. So the status got the generic variant of the list, which is derived > from the changer status. The two called each other until the stack > overflowed, and every operation that needs the changer status of a > virtual drive, like loading or unloading a tape, crashed the process. > > [...] Applied, thanks! [1/1] tape: virtual drive: fix endless recursion in changer status commit: 04d84d8f149f558e4796405c40b6423c3dffcffa