public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	ceph-devel@vger.kernel.org, Xiubo Li <xiubli@redhat.com>
Subject: [ceph-client:wip-fscrypt 6/64] net/ceph/osd_client.c:5702:51: error: too many arguments to function call, expected 3, have 4
Date: Tue, 31 May 2022 13:50:23 +0800	[thread overview]
Message-ID: <202205311337.ZFkD1cPR-lkp@intel.com> (raw)

tree:   https://github.com/ceph/ceph-client.git wip-fscrypt
head:   4a13fcc148c64143afe231bd0cae743b89c70177
commit: 0614a83e4f104460d5bdb8ba414ab69b8fdbdb39 [6/64] libceph: add sparse read support to OSD client
config: arm64-buildonly-randconfig-r002-20220531 (https://download.01.org/0day-ci/archive/20220531/202205311337.ZFkD1cPR-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c825abd6b0198fb088d9752f556a70705bc99dfd)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/ceph/ceph-client/commit/0614a83e4f104460d5bdb8ba414ab69b8fdbdb39
        git remote add ceph-client https://github.com/ceph/ceph-client.git
        git fetch --no-tags ceph-client wip-fscrypt
        git checkout 0614a83e4f104460d5bdb8ba414ab69b8fdbdb39
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash net/ceph/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> net/ceph/osd_client.c:5702:51: error: too many arguments to function call, expected 3, have 4
                   page = ceph_msg_data_next(cursor, &poff, &plen, &last);
                          ~~~~~~~~~~~~~~~~~~                       ^~~~~
   include/linux/ceph/messenger.h:527:14: note: 'ceph_msg_data_next' declared here
   struct page *ceph_msg_data_next(struct ceph_msg_data_cursor *cursor,
                ^
   1 error generated.


vim +5702 net/ceph/osd_client.c

  5694	
  5695	static void advance_cursor(struct ceph_msg_data_cursor *cursor, size_t len, bool zero)
  5696	{
  5697		while (len) {
  5698			struct page *page;
  5699			size_t poff, plen;
  5700			bool last = false;
  5701	
> 5702			page = ceph_msg_data_next(cursor, &poff, &plen, &last);
  5703			if (plen > len)
  5704				plen = len;
  5705			if (zero)
  5706				zero_user_segment(page, poff, poff + plen);
  5707			len -= plen;
  5708			ceph_msg_data_advance(cursor, plen);
  5709		}
  5710	}
  5711	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-05-31  5:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202205311337.ZFkD1cPR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jlayton@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=xiubli@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