patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Lennart Poettering <lennart@poettering.net>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
	Feli Flitzberg <feliflitzberg@proton.me>,
	systemd development <systemd-devel@lists.freedesktop.org>,
	Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [systemd-devel] With UEFI secure boot and dm-verity, how does one find the user data partition?
Date: Mon, 20 Oct 2025 22:27:43 +0200	[thread overview]
Message-ID: <aPabPx9wRN23i_7b@gardel-login> (raw)
In-Reply-To: <53262aac-8a40-4e77-97ea-e9847c0a82c9@gmail.com>

On Mo, 20.10.25 15:45, Demi Marie Obenour (demiobenour@gmail.com) wrote:

> >> Unfortunately this isn't what is needed.  Looks like UEFI variable
> >> storage is the best option.
> >
> > Partition UUID is (supposed to be) unique for every partition, so it
> > most certainly allows one to identify the device to which it belongs.
>
> I mixed up partition UUID and partition *type* UUID.
>
> What is the best way to use it?  The most obvious one requires that
> whenever a block device appears, one checks if either:
>
> - This has the correct partition UUID, and a device with the same
>   diskseq and the correct partition type UUID has appeared.
> - This has the correct partition type UUID, and a device with the
>   same diskseq and the correct partition UUID has appeared.
>
> Is there a simpler option?

The {Loader,Stub}DevicePartUUID efi var is passed in from the
firmware, which has no concept of a diskseq, hence it's purely a uuid.

systemd v258 and newer make the ESP booted from available via
/dev/disk/by-designator/esp and XBOOTLDR as
/dev/disk/by-designator/xbootldr as symlinks.

Lennart

--
Lennart Poettering, Berlin

      reply	other threads:[~2025-10-20 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b8a34c88-3dae-4ef2-bbad-0f0392d91a9d@gmail.com>
     [not found] ` <NYeXYP6ztNP_XNX333NJV5dMtyGq-bGAALIW-CF93loyJAuOLu4n3PlWon8IM_25jK090NiqcMQtXx4SVNcJuh3uSHBpCgu4A0aHwFKLK2s=@proton.me>
     [not found]   ` <14b8d7d5-1807-4814-8398-861883ebb3b0@gmail.com>
     [not found]     ` <573228c7-32be-4dcb-93e2-54e9b74c828c@gmail.com>
     [not found]       ` <2c453481-262f-407f-9a92-db3f4284042f@gmail.com>
     [not found]         ` <9ffb84b5-9c96-4899-ad8e-2401f387a3cd@gmail.com>
2025-10-20 18:22           ` [systemd-devel] With UEFI secure boot and dm-verity, how does one find the user data partition? Demi Marie Obenour
2025-10-20 19:10             ` Andrei Borzenkov
2025-10-20 19:45               ` Demi Marie Obenour
2025-10-20 20:27                 ` Lennart Poettering [this message]

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=aPabPx9wRN23i_7b@gardel-login \
    --to=lennart@poettering.net \
    --cc=arvidjaar@gmail.com \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.org \
    --cc=feliflitzberg@proton.me \
    --cc=systemd-devel@lists.freedesktop.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).