From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BFB0917C211; Sun, 1 Mar 2026 01:21:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772328114; cv=none; b=lCub0+YXzF5D0CtpYqKR3+DTJgo2fYYckHMGKIm4WVkdWMteYQivbpv0JbyLfk7XZW8357tcbIoYaij73+IiyehTNaEX1ryVWZhWOyytpXIiqSxuKqYHXdp81nlFlpWMc5axawFPLQvOGZ8vTDGVs9snsVOZGq4a+DiPP0oj6+E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772328114; c=relaxed/simple; bh=stuHyNvDx2dKkk43VzzX+Ii97SAG2WbEBlfAgbDqt3Y=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=d22BSGNzEAtSSkh7Y3f9dCh8jTB6ztDiW2qQ33lTlQz67PkENXJRguKFg+HmTHgEHF1qmeRGLnPQB2+AS3A/QzRhKwE5tbsMieBlTwQv4u/xTyjHlpLc30xtJz4MKKqJrdkL5BQeC75tjJF3Z/XvJHdCW+wcAtKFTyIFysmXM3s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KoqesAgv; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KoqesAgv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F3896C19421; Sun, 1 Mar 2026 01:21:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772328114; bh=stuHyNvDx2dKkk43VzzX+Ii97SAG2WbEBlfAgbDqt3Y=; h=From:To:Cc:Subject:Date:From; b=KoqesAgv7sU0vm9GsTUp+lolksQ2e8by7GeZPSDLet313UTGIr4iMHu9a/2chJVGZ wnsfAfiF+x1GvRBv1u+s8WGc3uB1eA5vctti+1vGyZWhSWfTytOPfv/5XDRFvNYQmJ 3zS/kDeg9roU9rga65m5jCLY5hxp/QZhzcMDY3J88SJaYJlL0aPMDPOWNTBl+8UE2v rHPgUoqaX1bcTiRQcUpw5j23MehhebavWw5tLRjELf+PfgKk3fFokoxJqHsEcPswe7 bUkPF3NLkk58WYB/1/HSDsCBiDW8dqn9tQW25wLkzZnZe3avv8idg1/XjilJny0+JX UTl3jdsQmo3yA== From: Sasha Levin To: stable@vger.kernel.org, schnelle@linux.ibm.com Cc: Benjamin Block , Farhan Ali , Heiko Carstens , linux-s390@vger.kernel.org Subject: FAILED: Patch "s390/pci: Handle futile config accesses of disabled devices directly" failed to apply to 6.12-stable tree Date: Sat, 28 Feb 2026 20:21:52 -0500 Message-ID: <20260301012152.1677954-1-sashal@kernel.org> X-Mailer: git-send-email 2.51.0 Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Patchwork-Hint: ignore X-stable: review Content-Transfer-Encoding: 8bit The patch below does not apply to the 6.12-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From 84d875e69818bed600edccb09be4a64b84a34a54 Mon Sep 17 00:00:00 2001 From: Niklas Schnelle Date: Thu, 8 Jan 2026 16:45:53 +0100 Subject: [PATCH] s390/pci: Handle futile config accesses of disabled devices directly On s390 PCI busses and slots with multiple functions may have holes because PCI functions are passed-through by the hypervisor on a per function basis and some functions may be in standby or reserved. This fact is indicated by returning true from the hypervisor_isolated_pci_functions() helper and triggers common code to scan all possible devfn values. Via pci_scan_single_device() this in turn causes config reads for the device and vendor IDs, even for PCI functions which are in standby and thereofore disabled. So far these futile config reads, as well as potentially writes, which can never succeed were handled by the PCI load/store instructions themselves. This works as the platform just returns an error for a disabled and thus not usable function handle. It does cause spamming of error logs and additional overhead though. Instead check if the used function handle is enabled in zpci_cfg_load() and zpci_cfg_write() and if not enable directly return -ENODEV. Also refactor zpci_cfg_load() and zpci_cfg_store() slightly to accommodate the new logic while meeting modern kernel style guidelines. Cc: stable@vger.kernel.org Fixes: a50297cf8235 ("s390/pci: separate zbus creation from scanning") Signed-off-by: Niklas Schnelle Reviewed-by: Benjamin Block Reviewed-by: Farhan Ali Signed-off-by: Heiko Carstens --- arch/s390/pci/pci.c | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c index 57f3980b98a92..7f44b0644a20e 100644 --- a/arch/s390/pci/pci.c +++ b/arch/s390/pci/pci.c @@ -231,24 +231,33 @@ int zpci_fmb_disable_device(struct zpci_dev *zdev) static int zpci_cfg_load(struct zpci_dev *zdev, int offset, u32 *val, u8 len) { u64 req = ZPCI_CREATE_REQ(zdev->fh, ZPCI_PCIAS_CFGSPC, len); + int rc = -ENODEV; u64 data; - int rc; + + if (!zdev_enabled(zdev)) + goto out_err; rc = __zpci_load(&data, req, offset); - if (!rc) { - data = le64_to_cpu((__force __le64) data); - data >>= (8 - len) * 8; - *val = (u32) data; - } else - *val = 0xffffffff; + if (rc) + goto out_err; + data = le64_to_cpu((__force __le64)data); + data >>= (8 - len) * 8; + *val = (u32)data; + return 0; + +out_err: + PCI_SET_ERROR_RESPONSE(val); return rc; } static int zpci_cfg_store(struct zpci_dev *zdev, int offset, u32 val, u8 len) { u64 req = ZPCI_CREATE_REQ(zdev->fh, ZPCI_PCIAS_CFGSPC, len); + int rc = -ENODEV; u64 data = val; - int rc; + + if (!zdev_enabled(zdev)) + return rc; data <<= (8 - len) * 8; data = (__force u64) cpu_to_le64(data); -- 2.51.0