From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [axboe-block:iter-ubuf 2/2] lib/iov_iter.c:1786:9: warning: no previous prototype for '__import_iovec_ubuf'
Date: Sat, 25 Mar 2023 10:39:52 +0800 [thread overview]
Message-ID: <202303251001.JGiCReZB-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git iter-ubuf
head: 8ccf20004bd671f70362eac93833c12f5ce89c66
commit: 8ccf20004bd671f70362eac93833c12f5ce89c66 [2/2] iov_iter: import single vector iovecs as ITER_UBUF
config: parisc-randconfig-r006-20230322 (https://download.01.org/0day-ci/archive/20230325/202303251001.JGiCReZB-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.1.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=8ccf20004bd671f70362eac93833c12f5ce89c66
git remote add axboe-block https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
git fetch --no-tags axboe-block iter-ubuf
git checkout 8ccf20004bd671f70362eac93833c12f5ce89c66
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303251001.JGiCReZB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/iov_iter.c:1786:9: warning: no previous prototype for '__import_iovec_ubuf' [-Wmissing-prototypes]
1786 | ssize_t __import_iovec_ubuf(int type, const struct iovec __user *uvec,
| ^~~~~~~~~~~~~~~~~~~
vim +/__import_iovec_ubuf +1786 lib/iov_iter.c
1782
1783 /*
1784 * Single segment iovec supplied by the user, import it as ITER_UBUF.
1785 */
> 1786 ssize_t __import_iovec_ubuf(int type, const struct iovec __user *uvec,
1787 struct iovec **iovp, struct iov_iter *i,
1788 bool compat)
1789 {
1790 struct iovec *iov = *iovp;
1791 ssize_t ret;
1792
1793 if (compat)
1794 ret = copy_compat_iovec_from_user(iov, uvec, 1);
1795 else
1796 ret = copy_iovec_from_user(iov, uvec, 1);
1797 if (unlikely(ret))
1798 return ret;
1799
1800 import_ubuf(type, iov->iov_base, iov->iov_len, i);
1801 *iovp = NULL;
1802 return i->count;
1803 }
1804
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-25 2:40 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=202303251001.JGiCReZB-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.