From: kbuild test robot <lkp@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: kbuild-all@01.org, Al Viro <viro@zeniv.linux.org.uk>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iov_iter: Fix out-of-bound access in iov_iter_advance()
Date: Fri, 1 Apr 2016 10:50:27 +0800 [thread overview]
Message-ID: <201604011017.8Kcs5xhn%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459421369-21286-1-git-send-email-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
Hi Takashi,
[auto build test WARNING on v4.6-rc1]
[also build test WARNING on next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Takashi-Iwai/iov_iter-Fix-out-of-bound-access-in-iov_iter_advance/20160331-185222
config: ia64-allnoconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
All warnings (new ones prefixed by >>):
lib/iov_iter.c: In function 'iov_iter_advance':
>> lib/iov_iter.c:514:3: warning: 'return' with a value, in function returning void
return 0;
^
vim +/return +514 lib/iov_iter.c
498 __copy_from_user_inatomic((p += v.iov_len) - v.iov_len,
499 v.iov_base, v.iov_len),
500 memcpy_from_page((p += v.bv_len) - v.bv_len, v.bv_page,
501 v.bv_offset, v.bv_len),
502 memcpy((p += v.iov_len) - v.iov_len, v.iov_base, v.iov_len)
503 )
504 kunmap_atomic(kaddr);
505 return bytes;
506 }
507 EXPORT_SYMBOL(iov_iter_copy_from_user_atomic);
508
509 void iov_iter_advance(struct iov_iter *i, size_t size)
510 {
511 if (unlikely(size > i->count))
512 size = i->count;
513 if (unlikely(!size))
> 514 return 0;
515 iterate_and_advance(i, size, v, 0, 0, 0)
516 }
517 EXPORT_SYMBOL(iov_iter_advance);
518
519 /*
520 * Return the count of just the current iov_iter segment.
521 */
522 size_t iov_iter_single_seg_count(const struct iov_iter *i)
---
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: 5532 bytes --]
prev parent reply other threads:[~2016-04-01 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:49 [PATCH] iov_iter: Fix out-of-bound access in iov_iter_advance() Takashi Iwai
2016-04-01 2:50 ` 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=201604011017.8Kcs5xhn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jslaby@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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.