From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Tony Luck <tony.luck@intel.com>,
linux-nvdimm@lists.01.org, Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 4/6] x86, memcpy_mcsafe: define copy_to_iter_mcsafe()
Date: Wed, 2 May 2018 06:49:44 +0800 [thread overview]
Message-ID: <201805020551.YQoEZubE%fengguang.wu@intel.com> (raw)
In-Reply-To: <152520752986.36522.6608981678390805141.stgit@dwillia2-desk3.amr.corp.intel.com>
Hi Dan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180501]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Dan-Williams/use-memcpy_mcsafe-for-copy_to_iter/20180502-045742
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
lib/iov_iter.c: In function 'copyout_mcsafe':
>> lib/iov_iter.c:146:7: error: implicit declaration of function 'copy_to_user_mcsafe'; did you mean 'copy_to_iter_mcsafe'? [-Werror=implicit-function-declaration]
n = copy_to_user_mcsafe((__force void *) to, from, n);
^~~~~~~~~~~~~~~~~~~
copy_to_iter_mcsafe
cc1: some warnings being treated as errors
vim +146 lib/iov_iter.c
141
142 static int copyout_mcsafe(void __user *to, const void *from, size_t n)
143 {
144 if (access_ok(VERIFY_WRITE, to, n)) {
145 kasan_check_read(from, n);
> 146 n = copy_to_user_mcsafe((__force void *) to, from, n);
147 }
148 return n;
149 }
150
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, linux-nvdimm@lists.01.org, x86@kernel.org,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Tony Luck <tony.luck@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@amacapital.net>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] x86, memcpy_mcsafe: define copy_to_iter_mcsafe()
Date: Wed, 2 May 2018 06:49:44 +0800 [thread overview]
Message-ID: <201805020551.YQoEZubE%fengguang.wu@intel.com> (raw)
In-Reply-To: <152520752986.36522.6608981678390805141.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Hi Dan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc3 next-20180501]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Dan-Williams/use-memcpy_mcsafe-for-copy_to_iter/20180502-045742
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
lib/iov_iter.c: In function 'copyout_mcsafe':
>> lib/iov_iter.c:146:7: error: implicit declaration of function 'copy_to_user_mcsafe'; did you mean 'copy_to_iter_mcsafe'? [-Werror=implicit-function-declaration]
n = copy_to_user_mcsafe((__force void *) to, from, n);
^~~~~~~~~~~~~~~~~~~
copy_to_iter_mcsafe
cc1: some warnings being treated as errors
vim +146 lib/iov_iter.c
141
142 static int copyout_mcsafe(void __user *to, const void *from, size_t n)
143 {
144 if (access_ok(VERIFY_WRITE, to, n)) {
145 kasan_check_read(from, n);
> 146 n = copy_to_user_mcsafe((__force void *) to, from, n);
147 }
148 return n;
149 }
150
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6302 bytes --]
next prev parent reply other threads:[~2018-05-01 22:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 20:45 [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter() Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 20:45 ` [PATCH 1/6] x86, memcpy_mcsafe: update labels in support of write fault handling Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 20:45 ` [PATCH 2/6] x86, memcpy_mcsafe: return bytes remaining Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 20:45 ` [PATCH 3/6] x86, memcpy_mcsafe: add write-protection-fault handling Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 20:45 ` [PATCH 4/6] x86, memcpy_mcsafe: define copy_to_iter_mcsafe() Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 22:17 ` kbuild test robot
2018-05-01 22:17 ` kbuild test robot
2018-05-01 22:49 ` kbuild test robot [this message]
2018-05-01 22:49 ` kbuild test robot
2018-05-01 20:45 ` [PATCH 5/6] dax: use copy_to_iter_mcsafe() in dax_iomap_actor() Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 20:45 ` [PATCH 6/6] x86, nfit_test: unit test for memcpy_mcsafe() Dan Williams
2018-05-01 20:45 ` Dan Williams
2018-05-01 21:05 ` [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter() Linus Torvalds
2018-05-01 21:05 ` Linus Torvalds
2018-05-01 23:02 ` Dan Williams
2018-05-01 23:02 ` Dan Williams
2018-05-01 23:28 ` Andy Lutomirski
2018-05-01 23:28 ` Andy Lutomirski
2018-05-01 23:31 ` Dan Williams
2018-05-01 23:31 ` Dan Williams
2018-05-02 0:09 ` Linus Torvalds
2018-05-02 0:09 ` Linus Torvalds
2018-05-02 2:25 ` Dan Williams
2018-05-02 2:25 ` Dan Williams
2018-05-02 2:53 ` Linus Torvalds
2018-05-02 2:53 ` Linus Torvalds
2018-05-02 3:02 ` Dan Williams
2018-05-02 3:02 ` Dan Williams
2018-05-02 3:13 ` Linus Torvalds
2018-05-02 3:13 ` Linus Torvalds
2018-05-02 3:20 ` Dan Williams
2018-05-02 3:20 ` Dan Williams
2018-05-02 3:22 ` Dan Williams
2018-05-02 3:22 ` Dan Williams
2018-05-02 3:33 ` Linus Torvalds
2018-05-02 3:33 ` Linus Torvalds
2018-05-02 4:00 ` Dan Williams
2018-05-02 4:00 ` Dan Williams
2018-05-02 4:14 ` Linus Torvalds
2018-05-02 4:14 ` Linus Torvalds
2018-05-02 5:37 ` Dan Williams
2018-05-02 5:37 ` Dan Williams
2018-05-02 16:19 ` Andy Lutomirski
2018-05-02 16:19 ` Andy Lutomirski
2018-05-02 17:47 ` Dan Williams
2018-05-02 17:47 ` Dan Williams
2018-05-02 8:30 ` Borislav Petkov
2018-05-02 8:30 ` Borislav Petkov
2018-05-02 13:52 ` Dan Williams
2018-05-02 13:52 ` Dan Williams
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=201805020551.YQoEZubE%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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 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.