Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5018467ybl; Mon, 9 Dec 2019 22:08:30 -0800 (PST) X-Google-Smtp-Source: APXvYqye5l7HuhLDOLwJaOLDUIbwDBXXG1YnfJcQ5g+dqPVdRTpeqVqH0gKUZNLrybfdqs2YhfrL X-Received: by 2002:a05:6830:2098:: with SMTP id y24mr24825987otq.312.1575958110184; Mon, 09 Dec 2019 22:08:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575958110; cv=none; d=google.com; s=arc-20160816; b=BHl6p2A3KdJmD0y6Cc3ckIsfK1yyZC221G6+dy2kh/fBy0tom5MgCAu4Xk3ocZ1TDk e3nGYcI5zDuUxE0XzEPCFK7fDBHghd5K1a0ryIoivF7AmN/PFSPH0pIVOZc/uzrtlcZm drGSL9haJtTv2wdoOK5QoIhxO8H2kkvlY2m5EPATprLTxx4OHMTpiD4hGEwx39w1VLg1 8h4fQSgD8xmtv5fo2BXMjw8knxuYdSeXA2MByLFONg1R/rIIjNGGbB79ezMYwsdre6oe Z3D32SifCFx/WCSqvEyp+qeo982FYeKbtmLnhWH9iexpVrDUP6llNTC2US10rx3sh4rO a6lg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from; bh=TrjTbQ+kTCJ8mfbRzLP6mQoX7x5IRGDeEYacbEtxknk=; b=ja3W3aP9P1RpwSURtPb8YgKeLX8476V295Y+CyVB0fSCaPYTwRRRwgLmptpbt52wSP BZaXzn4GsTF4SX/mQJxHsAsRXD++c5cbK6u7s2QPOxaJH8YhhCJt9NPYysuL1lzj+NZC ByKcN7kNmY+DCNJi2b4m6QqzAvfL/OdJibvWdfrZsiltiCmc8/zozoLKPwjRdBjzA8bS 4OI6r+AoV473IsnbFXpUc6chMst2/PzkBuYHhhLRAVJ86gNf2Ys3yrED8f28z/TYAuRQ MUQ2v3dPEBwiFY6MyDxYwXDEUddthbR1o/dkNqyTJsXt2NuHU2Xqtfjy4g58v26UuW/B MZ/g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i26si1380244otp.46.2019.12.09.22.08.18; Mon, 09 Dec 2019 22:08:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726979AbfLJGHP (ORCPT + 99 others); Tue, 10 Dec 2019 01:07:15 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:49460 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725942AbfLJGHO (ORCPT ); Tue, 10 Dec 2019 01:07:14 -0500 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 35A159D4EFD3133DFE18; Tue, 10 Dec 2019 14:07:11 +0800 (CST) Received: from HGHY4Z004218071.china.huawei.com (10.133.224.57) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id 14.3.439.0; Tue, 10 Dec 2019 14:07:00 +0800 From: Xiang Zheng To: , CC: , , , , , , , , , , Subject: [PATCH v3] PCI: Lock the pci_cfg_wait queue for the consistency of data Date: Tue, 10 Dec 2019 11:15:27 +0800 Message-ID: <20191210031527.40136-1-zhengxiang9@huawei.com> X-Mailer: git-send-email 2.15.1.windows.2 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.133.224.57] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 7ea7e98fd8d0 ("PCI: Block on access to temporarily unavailable pci device") suggests that the "pci_lock" is sufficient, and all the callers of pci_wait_cfg() are wrapped with the "pci_lock". However, since the commit cdcb33f98244 ("PCI: Avoid possible deadlock on pci_lock and p->pi_lock") merged, the accesses to the pci_cfg_wait queue are not safe anymore. This would cause kernel panic in a very low chance (See more detailed information from the below link). A "pci_lock" is insufficient and we need to hold an additional queue lock while read/write the wait queue. So let's use the add_wait_queue()/remove_wait_queue() instead of __add_wait_queue()/__remove_wait_queue(). Also move the wait queue functionality around the "schedule()" function to avoid reintroducing the deadlock addressed by "cdcb33f98244". Signed-off-by: Xiang Zheng Cc: Heyi Guo Cc: Biaoxiang Ye Link: https://lore.kernel.org/linux-pci/79827f2f-9b43-4411-1376-b9063b67aee3@huawei.com/ --- v3: Improve the commit subject and message. v2: Move the wait queue functionality around the "schedule()". --- drivers/pci/access.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pci/access.c b/drivers/pci/access.c index 2fccb5762c76..09342a74e5ea 100644 --- a/drivers/pci/access.c +++ b/drivers/pci/access.c @@ -207,14 +207,14 @@ static noinline void pci_wait_cfg(struct pci_dev *dev) { DECLARE_WAITQUEUE(wait, current); - __add_wait_queue(&pci_cfg_wait, &wait); do { set_current_state(TASK_UNINTERRUPTIBLE); raw_spin_unlock_irq(&pci_lock); + add_wait_queue(&pci_cfg_wait, &wait); schedule(); + remove_wait_queue(&pci_cfg_wait, &wait); raw_spin_lock_irq(&pci_lock); } while (dev->block_cfg_access); - __remove_wait_queue(&pci_cfg_wait, &wait); } /* Returns 0 on success, negative values indicate error. */ -- 2.19.1