mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>, Joerg Roedel <jroedel@suse.de>,
	Sasha Levin <sashal@kernel.org>,
	dwmw2@infradead.org, baolu.lu@linux.intel.com, joro@8bytes.org,
	will@kernel.org, iommu@lists.linux.dev
Subject: [PATCH AUTOSEL 5.19 07/29] iommu/vt-d: Handle race between registration and device probe
Date: Mon, 17 Oct 2022 20:08:16 -0400	[thread overview]
Message-ID: <20221018000839.2730954-7-sashal@kernel.org> (raw)
In-Reply-To: <20221018000839.2730954-1-sashal@kernel.org>

From: Robin Murphy <robin.murphy@arm.com>

[ Upstream commit c919739ce4721ecf7b96b99253b032df30fcf19b ]

Currently we rely on registering all our instances before initially
allowing any .probe_device calls via bus_set_iommu(). In preparation for
phasing out the latter, make sure we won't inadvertently return success
for a device associated with a known but not yet registered instance,
otherwise we'll run straight into iommu_group_get_for_dev() trying to
use NULL ops.

That also highlights an issue with intel_iommu_get_resv_regions() taking
dmar_global_lock from within a section where intel_iommu_init() already
holds it, which already exists via probe_acpi_namespace_devices() when
an ANDD device is probed, but gets more obvious with the upcoming change
to iommu_device_register(). Since they are both read locks it manages
not to deadlock in practice, and a more in-depth rework of this locking
is underway, so no attempt is made to address it here.

Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Link: https://lore.kernel.org/r/579f2692291bcbfc3ac64f7456fcff0d629af131.1660572783.git.robin.murphy@arm.com
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 drivers/iommu/intel/iommu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
index 3ed15e8ca677..690fad0d37f8 100644
--- a/drivers/iommu/intel/iommu.c
+++ b/drivers/iommu/intel/iommu.c
@@ -4586,7 +4586,7 @@ static struct iommu_device *intel_iommu_probe_device(struct device *dev)
 	u8 bus, devfn;
 
 	iommu = device_to_iommu(dev, &bus, &devfn);
-	if (!iommu)
+	if (!iommu || !iommu->iommu.ops)
 		return ERR_PTR(-ENODEV);
 
 	info = kzalloc(sizeof(*info), GFP_KERNEL);
-- 
2.35.1


  parent reply	other threads:[~2022-10-18  0:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  0:08 [PATCH AUTOSEL 5.19 01/29] crypto: qcom-rng - Fix qcom_rng_of_match unused warning Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 02/29] crypto: ccp - Add a quirk to firmware update Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 03/29] crypto: ccp - Initialize PSP when reading psp data file failed Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 04/29] gfs2: Switch from strlcpy to strscpy Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 05/29] powerpc/hw_breakpoint: Avoid relying on caller synchronization Sasha Levin
2022-10-18  1:04   ` Marco Elver
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 06/29] cgroup: Remove data-race around cgrp_dfl_visible Sasha Levin
2022-10-18  0:08 ` Sasha Levin [this message]
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 08/29] of/fdt: Don't calculate initrd size from DT if start > end Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 09/29] objtool,x86: Teach decode about LOOP* instructions Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 10/29] locking/rwsem: Disable preemption while trying for rwsem lock Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 11/29] gfs2: Check sb_bsize_shift after reading superblock Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 12/29] powerpc/64: don't refer nr_cpu_ids in asm code when it's undefined Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 13/29] m68knommu: fix non-specific 68328 choice interrupt build failure Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 14/29] m68knommu: fix non-mmu classic 68000 legacy timer tick selection Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 15/29] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 16/29] tracing/user_events: Use WRITE instead of READ for io vector import Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 17/29] tracing/user_events: Ensure user provided strings are safely formatted Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 18/29] of: Fix "dma-ranges" handling for bus controllers Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 19/29] x86/hyperv: Replace kmap() with kmap_local_page() Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 20/29] kmsan: disable instrumentation of unsupported common kernel code Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 21/29] kmsan: disable physical page merging in biovec Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 22/29] f2fs: fix wrong dirty page count when race between mmap and fallocate Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 23/29] f2fs: code clean and fix a type error Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 24/29] f2fs: fix to detect corrupted meta ino Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 25/29] 9p: trans_fd/p9_conn_cancel: drop client lock earlier Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 26/29] 9p/trans_fd: always use O_NONBLOCK read/write Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 27/29] net/9p: use a dedicated spinlock for trans_fd Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 28/29] virtio_pci: don't try to use intxif pin is zero Sasha Levin
2022-10-18  0:08 ` [PATCH AUTOSEL 5.19 29/29] cifs: replace kfree() with kfree_sensitive() for sensitive data Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221018000839.2730954-7-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jroedel@suse.de \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®