From: kernel test robot <lkp@intel.com>
To: Anna Schumaker <Anna.Schumaker@Netapp.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@redhat.com>
Subject: fs/nfsd/nfs4xdr.c:4657 nfsd4_encode_read_plus_hole() warn: inconsistent indenting
Date: Thu, 10 Jun 2021 05:03:15 +0800 [thread overview]
Message-ID: <202106100511.l1kajrsJ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 368094df48e680fa51cedb68537408cfa64b788e
commit: 2db27992dd565bf400658edc18f67aed0b6bc6cb NFSD: Add READ_PLUS hole segment encoding
date: 8 months ago
config: h8300-randconfig-m031-20210609 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
New smatch warnings:
fs/nfsd/nfs4xdr.c:4657 nfsd4_encode_read_plus_hole() warn: inconsistent indenting
Old smatch warnings:
fs/nfsd/nfs4xdr.c:679 nfsd4_decode_close() warn: ignoring unreachable code.
vim +4657 fs/nfsd/nfs4xdr.c
4642
4643 static __be32
4644 nfsd4_encode_read_plus_hole(struct nfsd4_compoundres *resp,
4645 struct nfsd4_read *read,
4646 unsigned long maxcount, u32 *eof)
4647 {
4648 struct file *file = read->rd_nf->nf_file;
4649 __be32 *p;
4650
4651 /* Content type, offset, byte count */
4652 p = xdr_reserve_space(&resp->xdr, 4 + 8 + 8);
4653 if (!p)
4654 return nfserr_resource;
4655
4656 *p++ = htonl(NFS4_CONTENT_HOLE);
> 4657 p = xdr_encode_hyper(p, read->rd_offset);
4658 p = xdr_encode_hyper(p, maxcount);
4659
4660 *eof = (read->rd_offset + maxcount) >= i_size_read(file_inode(file));
4661 return nfs_ok;
4662 }
4663
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28037 bytes --]
next reply other threads:[~2021-06-09 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 21:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-15 13:45 fs/nfsd/nfs4xdr.c:4657 nfsd4_encode_read_plus_hole() warn: inconsistent indenting kernel test robot
2020-10-28 23:24 kernel test robot
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=202106100511.l1kajrsJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=bfields@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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 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).