All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: cel@kernel.org
Cc: linux-nfs@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 1/4] nfs/blocklayout: Fix premature PR key unregistration
Date: Sat, 22 Jun 2024 07:03:25 +0200	[thread overview]
Message-ID: <20240622050324.GA11110@lst.de> (raw)
In-Reply-To: <20240621162227.215412-7-cel@kernel.org>

On Fri, Jun 21, 2024 at 12:22:29PM -0400, cel@kernel.org wrote:
> @@ -367,14 +391,7 @@ bl_parse_scsi(struct nfs_server *server, struct pnfs_block_dev *d,
>  		goto out_blkdev_put;
>  	}
>  
> -	error = ops->pr_register(file_bdev(d->bdev_file), 0, d->pr_key, true);
> -	if (error) {
> -		pr_err("pNFS: failed to register key for block device %s.",
> -				file_bdev(d->bdev_file)->bd_disk->disk_name);
> -		goto out_blkdev_put;
> -	}
> -
> -	d->pr_registered = true;
> +	d->pr_register = bl_pr_register_scsi;

I think this will break complex (slice, concat, stripe) volumes,
as we'll never call ->pr_register for them at all.  We'll also need
a register callback for them, which then calls into underlying
volume, similar to how bl_parse_deviceid works.  That would also
do away with the need for the d->pr_register callback, we could
just do the swithc on the volume types which might be more
efficient.  (the same is actually true for the ->map callback,
but that's a separate cleanup).


  reply	other threads:[~2024-06-22  5:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 16:22 [PATCH v2 0/4] Fixes for pNFS SCSI layout PR key registration cel
2024-06-21 16:22 ` [PATCH v2 1/4] nfs/blocklayout: Fix premature PR key unregistration cel
2024-06-22  5:03   ` Christoph Hellwig [this message]
2024-06-22 17:26     ` Chuck Lever
2024-06-23  7:36       ` Christoph Hellwig
2024-06-24 15:08         ` Chuck Lever
2024-06-21 16:22 ` [PATCH v2 2/4] nfs/blocklayout: Use bulk page allocation APIs cel
2024-06-22  5:08   ` Christoph Hellwig
2024-06-22 16:29     ` Chuck Lever
2024-06-21 16:22 ` [PATCH v2 3/4] nfs/blocklayout: Report only when /no/ device is found cel
2024-06-21 16:22 ` [PATCH v2 4/4] nfs/blocklayout: SCSI layout trace points for reservation key reg/unreg cel
2024-06-21 17:21   ` Anna Schumaker
2024-06-21 17:46     ` Chuck Lever III
2024-06-22  5:09   ` Christoph Hellwig
2024-06-21 18:03 ` [PATCH v2 0/4] Fixes for pNFS SCSI layout PR key registration Benjamin Coddington

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=20240622050324.GA11110@lst.de \
    --to=hch@lst.de \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.