From: Christoph Hellwig <hch@lst.de>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Christoph Hellwig <hch@lst.de>,
dm-devel@lists.linux.dev, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] dm: add support for get_unique_id
Date: Wed, 30 Oct 2024 14:52:14 +0100 [thread overview]
Message-ID: <20241030135214.GA28166@lst.de> (raw)
In-Reply-To: <f3657efae72f9abb93d3169308052e77bf0dbad6.1730292757.git.bcodding@redhat.com>
On Wed, Oct 30, 2024 at 08:57:56AM -0400, Benjamin Coddington wrote:
> This adds support to obtain a device's unique id through dm, similar to the
> existing ioctl and persistent resevation handling. We limit this to
> single-target devices.
>
> This enables knfsd to export pNFS SCSI luns that have been exported from
> multipath devices.
Is there anything that ensures that the underlying IDs actually
match?
> + struct dm_unique_id *dmuuid = data;
> + const struct block_device_operations *fops = dev->bdev->bd_disk->fops;
> +
> + if (fops->get_unique_id)
> + return fops->get_unique_id(dev->bdev->bd_disk, dmuuid->id, dmuuid->type);
> +
> + return 0;
Overly long line here. Also maybe just personal, but I find code easier
to read when the exit early condition is in the branch, e.g.
strut gendisk *disk = dev->bdev->bd_disk
if (!disk->fops->get_unique_id)
return 0;
return disk->fops->get_unique_id(disk, dmuuid->id, dmuuid->type);
next prev parent reply other threads:[~2024-10-30 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 12:57 [PATCH] dm: add support for get_unique_id Benjamin Coddington
2024-10-30 13:52 ` Christoph Hellwig [this message]
2024-10-30 14:05 ` Benjamin Coddington
2024-10-30 14:08 ` Christoph Hellwig
2024-10-30 14:19 ` Benjamin Coddington
2024-10-30 14:24 ` Mike Snitzer
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=20241030135214.GA28166@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=bcodding@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-nfs@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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