From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, axboe@fb.com, linux-nvdimm@ml01.01.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-block@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [PATCH] block: protect rw_page against device teardown
Date: Fri, 20 Nov 2015 08:32:04 +0800 [thread overview]
Message-ID: <201511200825.O2a2KLtg%fengguang.wu@intel.com> (raw)
In-Reply-To: <20151120001403.27823.74467.stgit@dwillia2-desk3.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
Hi Dan,
[auto build test ERROR on: block/for-next]
[also build test ERROR on: v4.4-rc1 next-20151119]
url: https://github.com/0day-ci/linux/commits/Dan-Williams/block-protect-rw_page-against-device-teardown/20151120-081807
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: xtensa-common_defconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
fs/block_dev.c: In function 'bdev_read_page':
>> fs/block_dev.c:389:2: error: implicit declaration of function 'blk_queue_enter' [-Werror=implicit-function-declaration]
rc = blk_queue_enter(bdev->bd_queue, GFP_KERNEL);
^
>> fs/block_dev.c:393:2: error: implicit declaration of function 'blk_queue_exit' [-Werror=implicit-function-declaration]
blk_queue_exit(bdev->bd_queue);
^
cc1: some warnings being treated as errors
vim +/blk_queue_enter +389 fs/block_dev.c
383 const struct block_device_operations *ops = bdev->bd_disk->fops;
384 int rc = -EOPNOTSUPP;
385
386 if (!ops->rw_page || bdev_get_integrity(bdev))
387 return rc;
388
> 389 rc = blk_queue_enter(bdev->bd_queue, GFP_KERNEL);
390 if (rc)
391 return rc;
392 rc = ops->rw_page(bdev, sector + get_start_sect(bdev), page, READ);
> 393 blk_queue_exit(bdev->bd_queue);
394 return rc;
395 }
396 EXPORT_SYMBOL_GPL(bdev_read_page);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 9576 bytes --]
next prev parent reply other threads:[~2015-11-20 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 0:14 [PATCH] block: protect rw_page against device teardown Dan Williams
2015-11-20 0:32 ` kbuild test robot [this message]
2015-11-20 0:51 ` Williams, Dan J
2015-11-20 18:12 ` Matthew Wilcox
2015-11-20 18:26 ` Williams, Dan J
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=201511200825.O2a2KLtg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).