public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] ublk: persistent device links
Date: Fri, 20 Feb 2026 12:54:33 +0800	[thread overview]
Message-ID: <aZfpCf5Vv0OaW7jN@fedora> (raw)
In-Reply-To: <20260216122730.144092-1-hare@kernel.org>

On Mon, Feb 16, 2026 at 01:27:30PM +0100, Hannes Reinecke wrote:
> Implement a 'uuid' parameter to export a device UUID in a sysfs
> attribute 'uuid'. This allows udev to create persistent device
> links for ublk devices:
> 
> KERNEL=="ublkb*", ATTRS{uuid}=="?*", SYMLINK+="disk/by-id/ublk-$attr{uuid}"

uuid is passed from ublk server, so the uniqueness has to be provided by
ublk server.

So far, the ublk device ID is guaranteed to be unique, can we export ublk
device id instead?

Or can you explain a bit if uuid is a must here for some special purpose?

Thanks, 
Ming


  reply	other threads:[~2026-02-20  4:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 12:27 [PATCH] ublk: persistent device links Hannes Reinecke
2026-02-20  4:54 ` Ming Lei [this message]
2026-02-20  7:33   ` Hannes Reinecke
2026-02-20 11:35 ` Ming Lei

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=aZfpCf5Vv0OaW7jN@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hare@kernel.org \
    --cc=linux-block@vger.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