Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Dan Williams (nvidia)" <djbw@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>,  Dan Williams <djbw@kernel.org>
Cc: linux-coco@lists.linux.dev,  linux-pci@vger.kernel.org,
	 driver-core@lists.linux.dev,  ankita@nvidia.com,
	 Alistair Francis <alistair.francis@wdc.com>,
	 Lukas Wunner <lukas@wunner.de>,
	 Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 01/15] netlink: specs: Introduce multi-message blobs for SPDM
Date: Fri, 10 Jul 2026 18:43:29 -0700	[thread overview]
Message-ID: <6a519fc19172_253dc100e8@djbw-dev.notmuch> (raw)
In-Reply-To: <m2y0flbuoa.fsf@gmail.com>

Donald Hunter wrote:
> Dan Williams <djbw@kernel.org> writes:
> 
> > The SPDM, Security Protocol and Data Model, underpins PCI device security
> > and other use cases. It defines objects that allow for verification of
> > device identity and configuration. These objects can be large in size 16MB.
> > Netlink is otherwise suitable to define the operations, with optional
> > parameters, and notifications for working with these objects. For example,
> > operations like "regenerate evidence with nonce", "mark evidence
> > validated", and "broadcast evidence / security state change events".
> >
> > A netlink 'blob' is introduced as a way to teach YNL that one instance of a
> > attribute may span multiple messages. It enables netlink to convey all the
> > data needed for verification and manipulation of SPDM transported evidence.
> >
> > The schema change to allows YNL to infer that an attribute may span
> 
> change to allows -> change allows

ack.

> > multiple messages and interrogate its length to preallocate an
> > appropriately sized receive buffer.
> >
> > The design direction to extend the netlink schema for a "multi-message
> > object receive" case was the result of this discussion [1].
> >
> > Cc: Alistair Francis <alistair.francis@wdc.com>
> > Cc: Lukas Wunner <lukas@wunner.de>
> > Cc: Jakub Kicinski <kuba@kernel.org>
> > Cc: Donald Hunter <donald.hunter@gmail.com>
> > Link: http://lore.kernel.org/20260318170014.6650d2bf@kernel.org [1]
> > Signed-off-by: Dan Williams <djbw@kernel.org>
> > ---
> >  Documentation/netlink/genetlink-legacy.yaml | 6 ++++++
> >  Documentation/netlink/genetlink.yaml        | 7 +++++++
> >  Documentation/netlink/netlink-raw.yaml      | 7 +++++++
> 
> I suggest you drop the changes to genetlink-legacy and netlink-raw
> because I don't think we want to support the blob functionality for
> legacy families.

Done.

> Can you also update Documentation/userspace-api/netlink/specs.rst to
> describe the multi-attr / bloblen API behaviour.

Added:

@@ -239,6 +239,16 @@ Boolean property signifying that the attribute may be present multiple times.
 Allowing an attribute to repeat is the recommended way of implementing arrays
 (no extra nesting).
 
+bloblen (multi-message binary blob)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+String property specified on a ``type: binary`` ``multi-attr: true``
+attribute to indicate that this single byte array may span multiple
+messages. The string names an attribute that indicates the final size of
+the blob when all messages are received. This differs from other ``type:
+binary`` ``multi-attr: true`` instances without bloblen where each
+message is an attribute boundary.
+
 byte-order
 ~~~~~~~~~~

  reply	other threads:[~2026-07-11  1:43 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 22:08 [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Dan Williams
2026-07-05 22:08 ` [PATCH 01/15] netlink: specs: Introduce multi-message blobs for SPDM Dan Williams
2026-07-05 22:13   ` sashiko-bot
2026-07-08 11:13   ` Donald Hunter
2026-07-11  1:43     ` Dan Williams (nvidia) [this message]
2026-07-08 13:23   ` Donald Hunter
2026-07-05 22:08 ` [PATCH 02/15] tools: ynl: Teach pyynl to handle blobs Dan Williams
2026-07-05 22:18   ` sashiko-bot
2026-07-08 13:48   ` Donald Hunter
2026-07-05 22:08 ` [PATCH 03/15] tools: ynl: Teach ynl_gen_c to validate and dump 'blob' attributes Dan Williams
2026-07-05 22:20   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 04/15] device core: Introduce "device evidence" over netlink Dan Williams
2026-07-05 22:20   ` sashiko-bot
2026-07-08 13:22   ` Donald Hunter
2026-07-05 22:08 ` [PATCH 05/15] device core: Add "device evidence" 'validate' command Dan Williams
2026-07-05 22:26   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 06/15] PCI/TSM: Add device evidence support Dan Williams
2026-07-05 22:16   ` sashiko-bot
2026-07-08  5:00   ` Alexey Kardashevskiy
2026-07-08 18:25     ` Dan Williams (nvidia)
2026-07-05 22:08 ` [PATCH 07/15] modules: Document the global async_probe parameter Dan Williams
2026-07-05 22:15   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 08/15] device core: Initial device trust infrastructure Dan Williams
2026-07-05 22:17   ` sashiko-bot
2026-07-06 13:45   ` Jason Gunthorpe
2026-07-05 22:08 ` [PATCH 09/15] PCI, device core: Move "untrusted" concept to DEVICE_TRUST_ADVERSARY Dan Williams
2026-07-05 22:25   ` sashiko-bot
2026-07-06 13:49   ` Jason Gunthorpe
2026-07-07 13:04   ` Robin Murphy
2026-07-05 22:08 ` [PATCH 10/15] PCI/TSM: Add device interface security LOCKED support Dan Williams
2026-07-05 22:25   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 11/15] PCI/TSM: Add device interface security RUN support Dan Williams
2026-07-05 22:21   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 12/15] PCI/TSM: Add device interface security DMA enable/disable Dan Williams
2026-07-05 22:25   ` sashiko-bot
2026-07-05 22:08 ` [PATCH 13/15] PCI, device core: Add private memory access for DEVICE_TRUST_TCB Dan Williams
2026-07-05 22:28   ` sashiko-bot
2026-07-06 12:42   ` Aneesh Kumar K.V
2026-07-08 18:06     ` Dan Williams (nvidia)
2026-07-08 18:10       ` Aneesh Kumar K.V
2026-07-09  6:32   ` Alexey Kardashevskiy
2026-07-09  7:38     ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 14/15] PCI/TSM: Create MMIO descriptors via TDISP Report Dan Williams
2026-07-05 22:24   ` sashiko-bot
2026-07-08  9:49   ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 15/15] PCI/TSM: Add relative MMIO offset support? Dan Williams
2026-07-05 22:25   ` sashiko-bot
2026-07-08  2:25   ` Alexey Kardashevskiy
2026-07-08 18:05     ` Dan Williams (nvidia)
2026-07-06 12:51 ` [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Jason Gunthorpe
2026-07-06 20:55   ` Dan Williams (nvidia)
2026-07-07 12:43     ` Jason Gunthorpe
2026-07-08  0:12       ` Dan Williams (nvidia)
2026-07-08 14:31         ` Jason Gunthorpe
2026-07-09  2:45           ` Dan Williams (nvidia)
2026-07-09 13:36             ` Jason Gunthorpe

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=6a519fc19172_253dc100e8@djbw-dev.notmuch \
    --to=djbw@kernel.org \
    --cc=alistair.francis@wdc.com \
    --cc=ankita@nvidia.com \
    --cc=donald.hunter@gmail.com \
    --cc=driver-core@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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