From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] memcg: fix a crash in wb_workfn when a device disappears
Date: Sat, 28 Dec 2019 06:32:49 +0800 [thread overview]
Message-ID: <201912280602.fO5HZ5FQ%lkp@intel.com> (raw)
In-Reply-To: <20191227194829.150110-1-tytso@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 3661 bytes --]
Hi Theodore,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on linus/master v5.5-rc3 next-20191220]
[cannot apply to tytso-fscrypt/master]
[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/Theodore-Ts-o/memcg-fix-a-crash-in-wb_workfn-when-a-device-disappears/20191228-035221
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 1f676247f36a4bdea134de5e8bc5041db9678c4e
config: nds32-allnoconfig (attached as .config)
compiler: nds32le-linux-gcc (GCC) 9.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=nds32
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from mm/fadvise.c:16:
include/linux/backing-dev.h: In function 'bdi_dev_name':
>> include/linux/backing-dev.h:513:9: error: implicit declaration of function 'dev_name' [-Werror=implicit-function-declaration]
513 | return dev_name(bdi->dev);
| ^~~~~~~~
>> include/linux/backing-dev.h:513:9: warning: returning 'int' from a function with return type 'const char *' makes pointer from integer without a cast [-Wint-conversion]
513 | return dev_name(bdi->dev);
| ^~~~~~~~~~~~~~~~~~
In file included from include/linux/node.h:18,
from include/linux/cpu.h:17,
from include/linux/perf_event.h:50,
from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:85,
from mm/fadvise.c:20:
include/linux/device.h: At top level:
include/linux/device.h:1370:27: error: conflicting types for 'dev_name'
1370 | static inline const char *dev_name(const struct device *dev)
| ^~~~~~~~
In file included from mm/fadvise.c:16:
include/linux/backing-dev.h:513:9: note: previous implicit declaration of 'dev_name' was here
513 | return dev_name(bdi->dev);
| ^~~~~~~~
cc1: some warnings being treated as errors
--
In file included from fs/super.c:32:
include/linux/backing-dev.h: In function 'bdi_dev_name':
>> include/linux/backing-dev.h:513:9: error: implicit declaration of function 'dev_name' [-Werror=implicit-function-declaration]
513 | return dev_name(bdi->dev);
| ^~~~~~~~
>> include/linux/backing-dev.h:513:9: warning: returning 'int' from a function with return type 'const char *' makes pointer from integer without a cast [-Wint-conversion]
513 | return dev_name(bdi->dev);
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/dev_name +513 include/linux/backing-dev.h
508
509 static inline const char *bdi_dev_name(struct backing_dev_info *bdi)
510 {
511 if (!bdi || !bdi->dev)
512 return bdi_unknown_name;
> 513 return dev_name(bdi->dev);
514 }
515
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 5229 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: kbuild-all@lists.01.org,
Linux Filesystem Development List
<linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] memcg: fix a crash in wb_workfn when a device disappears
Date: Sat, 28 Dec 2019 06:32:49 +0800 [thread overview]
Message-ID: <201912280602.fO5HZ5FQ%lkp@intel.com> (raw)
In-Reply-To: <20191227194829.150110-1-tytso@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 3584 bytes --]
Hi Theodore,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on linus/master v5.5-rc3 next-20191220]
[cannot apply to tytso-fscrypt/master]
[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/Theodore-Ts-o/memcg-fix-a-crash-in-wb_workfn-when-a-device-disappears/20191228-035221
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 1f676247f36a4bdea134de5e8bc5041db9678c4e
config: nds32-allnoconfig (attached as .config)
compiler: nds32le-linux-gcc (GCC) 9.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=nds32
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from mm/fadvise.c:16:
include/linux/backing-dev.h: In function 'bdi_dev_name':
>> include/linux/backing-dev.h:513:9: error: implicit declaration of function 'dev_name' [-Werror=implicit-function-declaration]
513 | return dev_name(bdi->dev);
| ^~~~~~~~
>> include/linux/backing-dev.h:513:9: warning: returning 'int' from a function with return type 'const char *' makes pointer from integer without a cast [-Wint-conversion]
513 | return dev_name(bdi->dev);
| ^~~~~~~~~~~~~~~~~~
In file included from include/linux/node.h:18,
from include/linux/cpu.h:17,
from include/linux/perf_event.h:50,
from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:85,
from mm/fadvise.c:20:
include/linux/device.h: At top level:
include/linux/device.h:1370:27: error: conflicting types for 'dev_name'
1370 | static inline const char *dev_name(const struct device *dev)
| ^~~~~~~~
In file included from mm/fadvise.c:16:
include/linux/backing-dev.h:513:9: note: previous implicit declaration of 'dev_name' was here
513 | return dev_name(bdi->dev);
| ^~~~~~~~
cc1: some warnings being treated as errors
--
In file included from fs/super.c:32:
include/linux/backing-dev.h: In function 'bdi_dev_name':
>> include/linux/backing-dev.h:513:9: error: implicit declaration of function 'dev_name' [-Werror=implicit-function-declaration]
513 | return dev_name(bdi->dev);
| ^~~~~~~~
>> include/linux/backing-dev.h:513:9: warning: returning 'int' from a function with return type 'const char *' makes pointer from integer without a cast [-Wint-conversion]
513 | return dev_name(bdi->dev);
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/dev_name +513 include/linux/backing-dev.h
508
509 static inline const char *bdi_dev_name(struct backing_dev_info *bdi)
510 {
511 if (!bdi || !bdi->dev)
512 return bdi_unknown_name;
> 513 return dev_name(bdi->dev);
514 }
515
---
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: 5229 bytes --]
next prev parent reply other threads:[~2019-12-27 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 19:48 [PATCH] memcg: fix a crash in wb_workfn when a device disappears Theodore Ts'o
2019-12-27 20:31 ` Theodore Ts'o
2019-12-27 21:16 ` kbuild test robot
2019-12-27 21:16 ` kbuild test robot
2019-12-27 21:19 ` Theodore Y. Ts'o
2019-12-27 21:19 ` Theodore Y. Ts'o
2019-12-27 22:32 ` kbuild test robot [this message]
2019-12-27 22:32 ` kbuild test robot
2019-12-28 0:52 ` [PATCH -v2] " Theodore Ts'o
2020-01-03 17:15 ` Theodore Y. Ts'o
2020-01-03 17:46 ` Chris Mason
2020-01-07 23:33 ` Andrew Morton
2020-01-08 2:12 ` Theodore Y. Ts'o
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=201912280602.fO5HZ5FQ%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.