From: kbuild test robot <lkp@intel.com>
To: Dima Zavin <dmitriyz@waymo.com>
Cc: kbuild-all@01.org, Christopher Lameter <cl@linux.com>,
Li Zefan <lizefan@huawei.com>, Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Cliff Spradlin <cspradlin@waymo.com>,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH v2] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()
Date: Sat, 29 Jul 2017 12:56:44 +0800 [thread overview]
Message-ID: <201707291220.DoV5J7Kf%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170727164608.12701-1-dmitriyz@waymo.com>
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
Hi Dima,
[auto build test WARNING on v4.12]
[cannot apply to cgroup/for-next linus/master v4.13-rc2 v4.13-rc1 next-20170728]
[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/Dima-Zavin/cpuset-fix-a-deadlock-due-to-incomplete-patching-of-cpusets_enabled/20170729-123852
config: i386-randconfig-x019-201730 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from kernel/sched/core.c:13:0:
include/linux/cpuset.h: In function 'read_mems_allowed_begin':
>> include/linux/cpuset.h:261:9: warning: 'return' with a value, in function returning void
return 0;
^
include/linux/cpuset.h:259:20: note: declared here
static inline void read_mems_allowed_begin(struct cpuset_mems_cookie *cookie)
^~~~~~~~~~~~~~~~~~~~~~~
vim +/return +261 include/linux/cpuset.h
58568d2a Miao Xie 2009-06-16 258
6b828cc9 Dima Zavin 2017-07-27 259 static inline void read_mems_allowed_begin(struct cpuset_mems_cookie *cookie)
c0ff7453 Miao Xie 2010-05-24 260 {
cc9a6c87 Mel Gorman 2012-03-21 @261 return 0;
c0ff7453 Miao Xie 2010-05-24 262 }
c0ff7453 Miao Xie 2010-05-24 263
:::::: The code at line 261 was first introduced by commit
:::::: cc9a6c8776615f9c194ccf0b63a0aa5628235545 cpuset: mm: reduce large amounts of memory barrier related damage v3
:::::: TO: Mel Gorman <mgorman@suse.de>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
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: 30137 bytes --]
prev parent reply other threads:[~2017-07-29 4:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 16:50 [RFC PATCH] mm/slub: " Dima Zavin
2017-07-26 17:02 ` Christopher Lameter
2017-07-26 19:52 ` Dima Zavin
2017-07-26 19:54 ` Dima Zavin
2017-07-27 16:46 ` [PATCH v2] cpuset: " Dima Zavin
2017-07-27 19:48 ` Andrew Morton
2017-07-27 21:41 ` Dima Zavin
2017-07-27 19:51 ` Andrew Morton
2017-07-27 21:41 ` Dima Zavin
2017-07-28 7:45 ` Vlastimil Babka
2017-07-28 8:48 ` Dima Zavin
2017-07-28 9:30 ` Peter Zijlstra
2017-07-28 14:05 ` Vlastimil Babka
2017-07-28 16:52 ` Dima Zavin
2017-07-31 4:01 ` [PATCH v3] " Dima Zavin
2017-07-31 4:04 ` Dima Zavin
2017-07-31 8:02 ` Vlastimil Babka
2017-07-31 9:05 ` Dima Zavin
2017-07-29 4:56 ` 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=201707291220.DoV5J7Kf%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=cspradlin@waymo.com \
--cc=dmitriyz@waymo.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mgorman@techsingularity.net \
--cc=penberg@kernel.org \
--cc=rientjes@google.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