From: Benny Halevy <bhalevy@panasas.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, sfaibish <sfaibish@emc.com>,
peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH] Return failure from bl_initialize_mountpoint if we can't get the device for the disk list.
Date: Wed, 03 Nov 2010 17:49:22 +0200 [thread overview]
Message-ID: <4CD18482.7090809@panasas.com> (raw)
In-Reply-To: <20101101174001.GA6731-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
On 2010-11-01 19:40, Jim Rees wrote:
> Signed-off-by: Jim Rees <rees@umich.edu>
Merged in pnfs-all-2.6.37-rc1-2010-11-03 (function renamed to bl_set_layoutdriver)
and in pnfs-all-2.6.36-2010-11-03.
Thanks!
Benny
> ---
> fs/nfs/blocklayout/blocklayout.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/blocklayout/blocklayout.c b/fs/nfs/blocklayout/blocklayout.c
> index 57a7f04..b3ab4cb 100644
> --- a/fs/nfs/blocklayout/blocklayout.c
> +++ b/fs/nfs/blocklayout/blocklayout.c
> @@ -677,7 +677,7 @@ static void free_blk_mountid(struct block_mount_id *mid)
> }
> }
>
> -/* This is mostly copied form the filelayout's get_device_info function.
> +/* This is mostly copied from the filelayout's get_device_info function.
> * It seems much of this should be at the generic pnfs level.
> */
> static struct pnfs_block_dev *
> @@ -796,8 +796,10 @@ bl_initialize_mountpoint(struct nfs_server *server, const struct nfs_fh *fh)
> bdev = nfs4_blk_get_deviceinfo(server, fh,
> &dlist->dev_id[i],
> &block_disklist);
> - if (!bdev)
> + if (!bdev) {
> + status = -ENODEV;
> goto out_error;
> + }
> spin_lock(&b_mt_id->bm_lock);
> list_add(&bdev->bm_node, &b_mt_id->bm_devlist);
> spin_unlock(&b_mt_id->bm_lock);
prev parent reply other threads:[~2010-11-03 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:40 [PATCH] Return failure from bl_initialize_mountpoint if we can't get the device for the disk list Jim Rees
[not found] ` <20101101174001.GA6731-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2010-11-03 15:49 ` Benny Halevy [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=4CD18482.7090809@panasas.com \
--to=bhalevy@panasas.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=sfaibish@emc.com \
/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.