linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peng Tao <tao.peng@primarydata.com>
Cc: kbuild-all@01.org,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	linux-nfs@vger.kernel.org,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Christoph Hellwig <hch@infradead.org>,
	Peng Tao <tao.peng@primarydata.com>
Subject: Re: [PATCH 6/6] nfs42: add NFS_IOC_CLONE_RANGE ioctl
Date: Mon, 28 Sep 2015 14:07:58 +0800	[thread overview]
Message-ID: <201509281437.JCMPpXnn%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443205479-13563-7-git-send-email-tao.peng@primarydata.com>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Hi Peng,

[auto build test results on v4.3-rc2 -- if it's inappropriate base, please ignore]

config: x86_64-randconfig-x005-09251258 (attached as .config)
reproduce:
  git checkout c66af182efac4295052614803f6e2fa5c6bb7a46
  # save the attached .config to linux build tree
  make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   fs/nfs/nfs4file.c: In function 'nfs4_ioctl':
>> fs/nfs/nfs4file.c:305:15: warning: unused variable 'argp' [-Wunused-variable]
     void __user *argp = (void __user *)arg;
                  ^

vim +/argp +305 fs/nfs/nfs4file.c

   289		return ret;
   290	}
   291	
   292	static long nfs42_ioctl_clone_range(struct file *dst_file, void __user *argp)
   293	{
   294		struct nfs_ioctl_clone_range_args args;
   295	
   296		if (copy_from_user(&args, argp, sizeof(args)))
   297			return -EFAULT;
   298	
   299		return nfs42_ioctl_clone(dst_file, args.src_fd, args.src_off, args.dst_off, args.count);
   300	}
   301	#endif /* CONFIG_NFS_V4_2 */
   302	
   303	long nfs4_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
   304	{
 > 305		void __user *argp = (void __user *)arg;
   306	
   307		switch (cmd) {
   308	#ifdef CONFIG_NFS_V4_2
   309		case NFS_IOC_CLONE:
   310			return nfs42_ioctl_clone(file, arg, 0, 0, 0);
   311		case NFS_IOC_CLONE_RANGE:
   312			return nfs42_ioctl_clone_range(file, argp);
   313	#endif

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24484 bytes --]

      reply	other threads:[~2015-09-28  6:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 18:24 [PATCH 0/6] nfs: add NFSv42 CLONE support Peng Tao
2015-09-25 18:24 ` [PATCH 1/6] nfs42: add CLONE xdr functions Peng Tao
2015-09-25 18:24 ` [PATCH 2/6] nfs42: add CLONE proc functions Peng Tao
2015-09-25 18:24 ` [PATCH 3/6] nfs42: add NFS_IOC_CLONE ioctl Peng Tao
2015-09-25 18:24 ` [PATCH 4/6] nfs: get clone_blksize when probing fsinfo Peng Tao
2015-09-25 18:24 ` [PATCH 5/6] nfs42: respect clone_blksize Peng Tao
2015-09-25 18:24 ` [PATCH 6/6] nfs42: add NFS_IOC_CLONE_RANGE ioctl Peng Tao
2015-09-28  6:07   ` kbuild test robot [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=201509281437.JCMPpXnn%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=anna.schumaker@netapp.com \
    --cc=hch@infradead.org \
    --cc=kbuild-all@01.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tao.peng@primarydata.com \
    --cc=trond.myklebust@primarydata.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).