From: kbuild test robot <lkp@intel.com>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: kbuild-all@lists.01.org, mhocko@suse.com,
mgorman@techsingularity.net, vbabka@suse.cz,
akpm@linux-foundation.org, yang.shi@linux.alibaba.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: migrate: handle freed page at the first place
Date: Wed, 13 Nov 2019 06:30:30 +0800 [thread overview]
Message-ID: <201911130608.0nwtgREV%lkp@intel.com> (raw)
In-Reply-To: <1573510165-113395-1-git-send-email-yang.shi@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 3459 bytes --]
Hi Yang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mmotm/master]
[also build test WARNING on v5.4-rc7 next-20191112]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Yang-Shi/mm-migrate-handle-freed-page-at-the-first-place/20191113-044923
base: git://git.cmpxchg.org/linux-mmotm.git master
config: x86_64-rhel-7.6-kasan (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:5:0,
from arch/x86/include/asm/bug.h:83,
from include/linux/bug.h:5,
from include/linux/mmdebug.h:5,
from include/linux/mm.h:9,
from include/linux/migrate.h:5,
from mm/migrate.c:16:
mm/migrate.c: In function 'migrate_pages':
>> include/linux/compiler.h:188:26: warning: 'newpage' may be used uninitialized in this function [-Wmaybe-uninitialized]
case 8: *(__u64 *)res = *(volatile __u64 *)p; break; \
^
mm/migrate.c:1170:15: note: 'newpage' was declared here
struct page *newpage;
^~~~~~~
vim +/newpage +188 include/linux/compiler.h
230fa253df6352 Christian Borntraeger 2014-11-25 181
d976441f44bc5d Andrey Ryabinin 2015-10-19 182 #define __READ_ONCE_SIZE \
d976441f44bc5d Andrey Ryabinin 2015-10-19 183 ({ \
d976441f44bc5d Andrey Ryabinin 2015-10-19 184 switch (size) { \
d976441f44bc5d Andrey Ryabinin 2015-10-19 185 case 1: *(__u8 *)res = *(volatile __u8 *)p; break; \
d976441f44bc5d Andrey Ryabinin 2015-10-19 186 case 2: *(__u16 *)res = *(volatile __u16 *)p; break; \
d976441f44bc5d Andrey Ryabinin 2015-10-19 187 case 4: *(__u32 *)res = *(volatile __u32 *)p; break; \
d976441f44bc5d Andrey Ryabinin 2015-10-19 @188 case 8: *(__u64 *)res = *(volatile __u64 *)p; break; \
d976441f44bc5d Andrey Ryabinin 2015-10-19 189 default: \
d976441f44bc5d Andrey Ryabinin 2015-10-19 190 barrier(); \
d976441f44bc5d Andrey Ryabinin 2015-10-19 191 __builtin_memcpy((void *)res, (const void *)p, size); \
d976441f44bc5d Andrey Ryabinin 2015-10-19 192 barrier(); \
d976441f44bc5d Andrey Ryabinin 2015-10-19 193 } \
d976441f44bc5d Andrey Ryabinin 2015-10-19 194 })
d976441f44bc5d Andrey Ryabinin 2015-10-19 195
:::::: The code at line 188 was first introduced by commit
:::::: d976441f44bc5d48635d081d277aa76556ffbf8b compiler, atomics, kasan: Provide READ_ONCE_NOCHECK()
:::::: TO: Andrey Ryabinin <aryabinin@virtuozzo.com>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 48332 bytes --]
prev parent reply other threads:[~2019-11-12 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 22:09 Yang Shi
2019-11-11 23:18 ` Andrew Morton
2019-11-12 0:02 ` Yang Shi
2019-11-12 8:04 ` Michal Hocko
2019-11-12 11:37 ` Michal Hocko
2019-11-12 18:29 ` Yang Shi
2019-11-12 22:30 ` 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=201911130608.0nwtgREV%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
--cc=yang.shi@linux.alibaba.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