From: "J. Bruce Fields" <bfields@fieldses.org>
To: Scott Mayhew <smayhew@redhat.com>
Cc: jlayton@kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: make nfsd4_scsi_identify_device retry with a larger buffer
Date: Mon, 7 May 2018 14:45:20 -0400 [thread overview]
Message-ID: <20180507184520.GF4749@fieldses.org> (raw)
In-Reply-To: <20180507130131.7221-1-smayhew@redhat.com>
On Mon, May 07, 2018 at 09:01:31AM -0400, Scott Mayhew wrote:
> nfsd4_scsi_identify_device() performs a single IDENTIFY command for the
> device identification VPD page using a small buffer. If the reply is
> too large to fit in this buffer then the GETDEVICEINFO reply will not
> contain any info for the SCSI volume aside from the registration key.
> This can happen for example if the device has descriptors using long
> SCSI name strings.
>
> When the initial reply from the device indicates a larger buffer is
> needed, retry once using the page length from that reply.
Looks good, but how did you choose 65532 as the maximum? Does the scsi
layer give us any maximum?
Also, I don't know why this is bothering me, but: I'd prefer "buflen" to
"bufflen".
--b.
>
> Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> ---
> fs/nfsd/blocklayout.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/fs/nfsd/blocklayout.c b/fs/nfsd/blocklayout.c
> index 70b8bf7..0cd9249 100644
> --- a/fs/nfsd/blocklayout.c
> +++ b/fs/nfsd/blocklayout.c
> @@ -216,13 +216,14 @@ static int nfsd4_scsi_identify_device(struct block_device *bdev,
> struct request_queue *q = bdev->bd_disk->queue;
> struct request *rq;
> struct scsi_request *req;
> - size_t bufflen = 252, len, id_len;
> + size_t bufflen = 252, maxlen = 65532, len, id_len;
> u8 *buf, *d, type, assoc;
> - int error;
> + int retries = 1, error;
>
> if (WARN_ON_ONCE(!blk_queue_scsi_passthrough(q)))
> return -EINVAL;
>
> +again:
> buf = kzalloc(bufflen, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
> @@ -255,9 +256,16 @@ static int nfsd4_scsi_identify_device(struct block_device *bdev,
>
> len = (buf[2] << 8) + buf[3] + 4;
> if (len > bufflen) {
> - pr_err("pNFS: INQUIRY 0x83 response invalid (len = %zd)\n",
> - len);
> - goto out_put_request;
> + if (len < maxlen && retries--) {
> + blk_put_request(rq);
> + kfree(buf);
> + bufflen = len;
> + goto again;
> + } else {
> + pr_err("pNFS: INQUIRY 0x83 response invalid (len = %zd)\n",
> + len);
> + goto out_put_request;
> + }
> }
>
> d = buf + 4;
> --
> 2.9.5
next prev parent reply other threads:[~2018-05-07 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 13:01 [PATCH] nfsd: make nfsd4_scsi_identify_device retry with a larger buffer Scott Mayhew
2018-05-07 18:45 ` J. Bruce Fields [this message]
2018-05-07 20:17 ` Scott Mayhew
2018-05-10 14:16 ` J. Bruce Fields
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=20180507184520.GF4749@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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 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).