linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Sergey Bashirov <sergeybashirov@gmail.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Konstantin Evtushenko <koevtushenko@yandex.com>
Subject: Re: [PATCH v4 1/2] nfsd: Drop dprintk in blocklayout xdr functions
Date: Sat, 21 Jun 2025 14:46:58 -0400	[thread overview]
Message-ID: <369459745a8f8e43f80c47bae554829dad8f635c.camel@kernel.org> (raw)
In-Reply-To: <20250621165409.147744-2-sergeybashirov@gmail.com>

On Sat, 2025-06-21 at 19:52 +0300, Sergey Bashirov wrote:
> Minor clean up. Instead of dprintk there are appropriate error codes.
> 
> Signed-off-by: Sergey Bashirov <sergeybashirov@gmail.com>
> ---
>  fs/nfsd/blocklayoutxdr.c | 40 +++++++---------------------------------
>  1 file changed, 7 insertions(+), 33 deletions(-)
> 
> diff --git a/fs/nfsd/blocklayoutxdr.c b/fs/nfsd/blocklayoutxdr.c
> index 669ff8e6e966..bcf21fde9120 100644
> --- a/fs/nfsd/blocklayoutxdr.c
> +++ b/fs/nfsd/blocklayoutxdr.c
> @@ -139,28 +139,19 @@ nfsd4_block_decode_layoutupdate(__be32 *p, u32 len, struct iomap **iomapp,
>  	struct iomap *iomaps;
>  	u32 nr_iomaps, i;
>  
> -	if (len < sizeof(u32)) {
> -		dprintk("%s: extent array too small: %u\n", __func__, len);
> +	if (len < sizeof(u32))
>  		return nfserr_bad_xdr;
> -	}
>  	len -= sizeof(u32);
> -	if (len % PNFS_BLOCK_EXTENT_SIZE) {
> -		dprintk("%s: extent array invalid: %u\n", __func__, len);
> +	if (len % PNFS_BLOCK_EXTENT_SIZE)
>  		return nfserr_bad_xdr;
> -	}
>  
>  	nr_iomaps = be32_to_cpup(p++);
> -	if (nr_iomaps != len / PNFS_BLOCK_EXTENT_SIZE) {
> -		dprintk("%s: extent array size mismatch: %u/%u\n",
> -			__func__, len, nr_iomaps);
> +	if (nr_iomaps != len / PNFS_BLOCK_EXTENT_SIZE)
>  		return nfserr_bad_xdr;
> -	}
>  
>  	iomaps = kcalloc(nr_iomaps, sizeof(*iomaps), GFP_KERNEL);
> -	if (!iomaps) {
> -		dprintk("%s: failed to allocate extent array\n", __func__);
> +	if (!iomaps)
>  		return nfserr_delay;
> -	}
>  
>  	for (i = 0; i < nr_iomaps; i++) {
>  		struct pnfs_block_extent bex;
> @@ -170,26 +161,18 @@ nfsd4_block_decode_layoutupdate(__be32 *p, u32 len, struct iomap **iomapp,
>  
>  		p = xdr_decode_hyper(p, &bex.foff);
>  		if (bex.foff & (block_size - 1)) {
> -			dprintk("%s: unaligned offset 0x%llx\n",
> -				__func__, bex.foff);
>  			goto fail;
>  		}
>  		p = xdr_decode_hyper(p, &bex.len);
>  		if (bex.len & (block_size - 1)) {
> -			dprintk("%s: unaligned length 0x%llx\n",
> -				__func__, bex.foff);
>  			goto fail;
>  		}
>  		p = xdr_decode_hyper(p, &bex.soff);
>  		if (bex.soff & (block_size - 1)) {
> -			dprintk("%s: unaligned disk offset 0x%llx\n",
> -				__func__, bex.soff);
>  			goto fail;
>  		}
>  		bex.es = be32_to_cpup(p++);
>  		if (bex.es != PNFS_BLOCK_READWRITE_DATA) {
> -			dprintk("%s: incorrect extent state %d\n",
> -				__func__, bex.es);
>  			goto fail;
>  		}
>  
> @@ -231,38 +214,29 @@ nfsd4_scsi_decode_layoutupdate(__be32 *p, u32 len, struct iomap **iomapp,
>  	struct iomap *iomaps;
>  	u32 nr_iomaps, expected, i;
>  
> -	if (len < sizeof(u32)) {
> -		dprintk("%s: extent array too small: %u\n", __func__, len);
> +	if (len < sizeof(u32))
>  		return nfserr_bad_xdr;
> -	}
>  
>  	nr_iomaps = be32_to_cpup(p++);
>  	expected = sizeof(__be32) + nr_iomaps * PNFS_SCSI_RANGE_SIZE;
> -	if (len != expected) {
> -		dprintk("%s: extent array size mismatch: %u/%u\n",
> -			__func__, len, expected);
> +	if (len != expected)
>  		return nfserr_bad_xdr;
> -	}
>  
>  	iomaps = kcalloc(nr_iomaps, sizeof(*iomaps), GFP_KERNEL);
> -	if (!iomaps) {
> -		dprintk("%s: failed to allocate extent array\n", __func__);
> +	if (!iomaps)
>  		return nfserr_delay;
> -	}
>  
>  	for (i = 0; i < nr_iomaps; i++) {
>  		u64 val;
>  
>  		p = xdr_decode_hyper(p, &val);
>  		if (val & (block_size - 1)) {
> -			dprintk("%s: unaligned offset 0x%llx\n", __func__, val);
>  			goto fail;
>  		}
>  		iomaps[i].offset = val;
>  
>  		p = xdr_decode_hyper(p, &val);
>  		if (val & (block_size - 1)) {
> -			dprintk("%s: unaligned length 0x%llx\n", __func__, val);
>  			goto fail;
>  		}
>  		iomaps[i].length = val;

Looks sane, and most of these dprintks aren't terribly helpful for day
to day usage.

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-06-21 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21 16:52 [PATCH v4 0/2] nfsd: Implement large extent array support in pNFS Sergey Bashirov
2025-06-21 16:52 ` [PATCH v4 1/2] nfsd: Drop dprintk in blocklayout xdr functions Sergey Bashirov
2025-06-21 18:46   ` Jeff Layton [this message]
2025-06-23  7:34   ` Christoph Hellwig
2025-06-21 16:52 ` [PATCH v4 2/2] nfsd: Implement large extent array support in pNFS Sergey Bashirov
2025-06-21 19:08   ` Jeff Layton
2025-06-23  7:41   ` Christoph Hellwig
2025-06-23 13:50 ` [PATCH v4 0/2] " Chuck Lever

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=369459745a8f8e43f80c47bae554829dad8f635c.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=hch@infradead.org \
    --cc=koevtushenko@yandex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=sergeybashirov@gmail.com \
    --cc=tom@talpey.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).