Re: linux-next: manual merge of the akpm-current tree with the block tree

From: kbuild test robot
Date: Sun Nov 01 2015 - 11:05:58 EST


Hi Stephen,

[auto build test ERROR on block/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url: https://github.com/0day-ci/linux/commits/Stephen-Rothwell/linux-next-manual-merge-of-the-akpm-current-tree-with-the-block-tree/20151101-235406
config: x86_64-randconfig-x019-201544 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64

All errors (new ones prefixed by >>):

block/blk-core.c: In function 'blk_queue_enter':
>> block/blk-core.c:641:8: error: implicit declaration of function 'gfpflags_allow_blocking' [-Werror=implicit-function-declaration]
if (!gfpflags_allow_blocking(gfp))
^
In file included from include/linux/linkage.h:4:0,
from include/linux/kernel.h:6,
from block/blk-core.c:14:
block/blk-core.c: In function 'generic_make_request':
>> block/blk-core.c:2041:33: error: '__GFP_RECLAIM' undeclared (first use in this function)
if (likely(blk_queue_enter(q, __GFP_RECLAIM) == 0)) {
^
include/linux/compiler.h:165:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
block/blk-core.c:2041:33: note: each undeclared identifier is reported only once for each function it appears in
if (likely(blk_queue_enter(q, __GFP_RECLAIM) == 0)) {
^
include/linux/compiler.h:165:40: note: in definition of macro 'likely'
# define likely(x) __builtin_expect(!!(x), 1)
^
cc1: some warnings being treated as errors

vim +/gfpflags_allow_blocking +641 block/blk-core.c

635 while (true) {
636 int ret;
637
638 if (percpu_ref_tryget_live(&q->q_usage_counter))
639 return 0;
640
> 641 if (!gfpflags_allow_blocking(gfp))
642 return -EBUSY;
643
644 ret = wait_event_interruptible(q->mq_freeze_wq,

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation

Attachment: .config.gz
Description: Binary data