From: Leon Romanovsky <leon@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Johan Hovold <johan@kernel.org>,
Eric Dumazet <edumazet@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Nikhil Agarwal <nikhil.agarwal@amd.com>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>,
Chris Lu <chris.lu@mediatek.com>, Mans Rullgard <mans@mansr.com>,
Alan Stern <stern@rowland.harvard.edu>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Andrew Morton <akpm@osdl.org>, Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
linux-input@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-usb@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-doc@vger.kernel.org, linux-pci@vger.kernel.org,
iommu@lists.linux.dev, linux-coco@lists.linux.dev,
Alexey Kardashevskiy <aik@amd.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-sound@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: [PATCH v3 00/31] driver core: Authorize device trust before driver binding
Date: Wed, 18 Nov 2026 21:26:30 +0200 [thread overview]
Message-ID: <20261118-device-trust-core-v3-0-d655875c4bfb@nvidia.com> (raw)
Device trust policies need to precede driver setup, including manual
attachment, so userspace can authorize devices before they operate.
This series introduces device trust policy, authorization, and lifetime
commitment. Authorization does not reconfigure ATS capabilities or replace
IOMMU domains selected during discovery and further ATS and IOMMU integration
will follow in a separate series.
The table below tries to summarize the possible kernel command line
options and system behavior after that:
Command line Initial behavior
---------------------------------- ---------------------------------------
No device_trust options General: existing driver binding.
PCI: existing ACPI/topology
restrictions.
USB: existing authorized sysfs flow.
device_trust.default=default General: use each bus's initial policy.
PCI: use platform trust policy; keep
existing domain and ATS decisions.
USB: devices and interfaces denied by
USB defaults wait for authorization
before binding.
device_trust.default=blocked General: block driver binding until
authorization.
PCI: keep existing domain and ATS
decisions while binding is blocked.
USB: leave devices and interfaces
unbound until authorized.
device_trust.default=adversary General: allow binding as an adversary.
PCI: keep existing platform-based DMA
handling, domain and ATS decisions.
USB: allow binding as an adversary,
overriding USB authorization
defaults.
device_trust.default=unrestricted General: allow unrestricted binding;
freeze trust policy changes.
PCI: unrestricted active trust; keep
existing domain and ATS decisions.
USB: authorize devices and interfaces
regardless of USB defaults.
device_trust=... General: matching rules select policy;
or device_trust.driver=... unmatched devices stay blocked.
without an explicit default PCI: rules select admission policy;
existing domain and ATS decisions
remain.
USB: matching rules select device or
interface policy.
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
Changes in v3:
- Rewrote all commit messages
- Split USB patches to smaller chunks
- Introduced special device attach function which works only in
untrusted mode
- Remove the special PHY -EBUSY IRQ handling.
- Clarify that further ATS and IOMMU integration follows separately.
- Link to v2: https://patch.msgid.link/20261109-device-trust-core-v2-0-3b12d9a9f861@nvidia.com
Changes in v2:
- Replace the serio and PHY attachment conversions with
device_driver_attach_unrestricted(), restricted to device_trust.default=unrestricted.
- Add USB authorization on top of device trust: export
device_trust_set_policy() and convert the USB authorized attributes.
- Documentation and commit messages fixes
- Small USB patches rewrote and split
- Link to v1: https://patch.msgid.link/20261105-device-trust-core-v1-0-1e536825b4eb@nvidia.com
---
Leon Romanovsky (31):
wifi: mac80211_hwsim: lock device for manual driver binding
Bluetooth: btusb: Fix MediaTek ISO claim locking
USB: Lock interfaces during manual driver binding
USB: serial: Register USB drivers with their owning module
USB: Reject claims of DT-disabled interfaces
USB: Release interface claims according to binding state
USB: Reject claims after interface registration failure
ALSA: usb-audio: Release interface claims when probe fails
USB: Pin modules for unregistered interface claims
USB: Add helpers to release unpublished interface claims
USB: Unwind interface claims after registration or binding failure
PNP: Attach card devices through the driver core
cdx: Propagate DMA configuration errors
driver core: Report deferred probes through sysfs drivers_probe
driver core: Add a compatibility API for manual driver attachment
Input: gameport - use the compatibility driver attachment API
Input: serio - use the compatibility driver attachment API
net: phy: Use the compatibility driver attachment API
driver core: Introduce a generic device trust level
driver core: Expose device trust authorization interfaces
driver core: Accept device trust policy on the kernel command line
driver core: Accept device trust policy by driver name
driver core: Expose committed device trust level
driver core: Cover trust authorization and binding with KUnit
driver core: Document trust admission and initrd authorization
PCI: Use device trust for platform restrictions
iommu: Use device trust for DMA restrictions
driver core: Allow driver attachment with the device lock held
USB: Retain the result of configuration requests
USB: Authorize interfaces through device trust
USB: Authorize devices through device trust
Documentation/ABI/testing/sysfs-bus-drivers-probe | 14 +
Documentation/ABI/testing/sysfs-bus-usb | 18 +
Documentation/ABI/testing/sysfs-devices-trust | 37 +
Documentation/admin-guide/kernel-parameters.txt | 35 +
.../driver-api/driver-model/device-trust.rst | 323 +++
Documentation/driver-api/driver-model/index.rst | 1 +
Documentation/usb/authorization.rst | 37 +
MAINTAINERS | 2 +
drivers/base/Makefile | 2 +-
drivers/base/base.h | 52 +
drivers/base/bus.c | 9 +-
drivers/base/core.c | 52 +-
drivers/base/dd.c | 192 +-
drivers/base/test/Makefile | 1 +
drivers/base/test/device-trust-test.c | 2461 ++++++++++++++++++++
drivers/base/trust.c | 508 ++++
drivers/bluetooth/btusb_main.c | 57 +-
drivers/cdx/cdx.c | 2 +-
drivers/input/gameport/gameport.c | 22 +-
drivers/input/serio/serio.c | 29 +-
drivers/iommu/amd/iommu.c | 3 +-
drivers/iommu/dma-iommu.c | 14 +-
drivers/iommu/intel/iommu.c | 14 +-
drivers/iommu/iommu.c | 9 +-
drivers/net/phy/phy_device.c | 28 +-
drivers/net/wireless/virtual/mac80211_hwsim_main.c | 2 +
drivers/pci/ats.c | 4 +-
drivers/pci/pci.c | 5 +-
drivers/pci/probe.c | 18 +-
drivers/pci/quirks.c | 7 +-
drivers/pnp/card.c | 12 +-
drivers/usb/core/driver.c | 121 +-
drivers/usb/core/generic.c | 2 +-
drivers/usb/core/hub.c | 39 +-
drivers/usb/core/message.c | 106 +-
drivers/usb/core/sysfs.c | 9 +-
drivers/usb/core/trace.h | 2 +-
drivers/usb/core/usb.c | 5 +
drivers/usb/core/usb.h | 6 +-
drivers/usb/serial/usb-serial.c | 4 +-
include/linux/device.h | 21 +
include/linux/device/bus.h | 10 +
include/linux/device/trust.h | 54 +
include/linux/pci.h | 18 +-
include/linux/usb.h | 25 +-
include/linux/usb/serial.h | 4 +-
sound/usb/card.c | 7 +
47 files changed, 4190 insertions(+), 213 deletions(-)
---
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
change-id: 20260915-device-trust-core-12934e618489
Best regards,
--
Leon Romanovsky <leonro@nvidia.com>
next reply other threads:[~2026-11-18 19:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 19:26 Leon Romanovsky [this message]
2026-11-18 19:26 ` [PATCH v3 01/31] wifi: mac80211_hwsim: lock device for manual driver binding Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 02/31] Bluetooth: btusb: Fix MediaTek ISO claim locking Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 03/31] USB: Lock interfaces during manual driver binding Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 04/31] USB: serial: Register USB drivers with their owning module Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 05/31] USB: Reject claims of DT-disabled interfaces Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 06/31] USB: Release interface claims according to binding state Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 07/31] USB: Reject claims after interface registration failure Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 08/31] ALSA: usb-audio: Release interface claims when probe fails Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 09/31] USB: Pin modules for unregistered interface claims Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 10/31] USB: Add helpers to release unpublished " Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 11/31] USB: Unwind interface claims after registration or binding failure Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 12/31] PNP: Attach card devices through the driver core Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 13/31] cdx: Propagate DMA configuration errors Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 14/31] driver core: Report deferred probes through sysfs drivers_probe Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 15/31] driver core: Add a compatibility API for manual driver attachment Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 16/31] Input: gameport - use the compatibility driver attachment API Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 17/31] Input: serio " Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 18/31] net: phy: Use " Leon Romanovsky
2026-11-18 20:21 ` Andrew Lunn
2026-11-18 19:26 ` [PATCH v3 19/31] driver core: Introduce a generic device trust level Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 20/31] driver core: Expose device trust authorization interfaces Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 21/31] driver core: Accept device trust policy on the kernel command line Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 22/31] driver core: Accept device trust policy by driver name Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 23/31] driver core: Expose committed device trust level Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 24/31] driver core: Cover trust authorization and binding with KUnit Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 25/31] driver core: Document trust admission and initrd authorization Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 26/31] PCI: Use device trust for platform restrictions Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 27/31] iommu: Use device trust for DMA restrictions Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 28/31] driver core: Allow driver attachment with the device lock held Leon Romanovsky
2026-11-18 19:26 ` [PATCH v3 29/31] USB: Retain the result of configuration requests Leon Romanovsky
2026-11-18 19:27 ` [PATCH v3 30/31] USB: Authorize interfaces through device trust Leon Romanovsky
2026-11-18 19:27 ` [PATCH v3 31/31] USB: Authorize devices " Leon Romanovsky
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=20261118-device-trust-core-v3-0-d655875c4bfb@nvidia.com \
--to=leon@kernel.org \
--cc=aik@amd.com \
--cc=akpm@linux-foundation.org \
--cc=akpm@osdl.org \
--cc=andrew@lunn.ch \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=chris.lu@mediatek.com \
--cc=corbet@lwn.net \
--cc=cornelia.huck@de.ibm.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=dwmw2@infradead.org \
--cc=edumazet@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregkh@suse.de \
--cc=hkallweit1@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jeff@garzik.org \
--cc=jgg@ziepe.ca \
--cc=johan@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=joro@8bytes.org \
--cc=kuba@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=mans@mansr.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=pabeni@redhat.com \
--cc=perex@perex.cz \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=stern@rowland.harvard.edu \
--cc=suravee.suthikulpanit@amd.com \
--cc=tiwai@suse.com \
--cc=vasant.hegde@amd.com \
--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