From: kbuild test robot <lkp@intel.com>
To: Jan Kara <jack@suse.com>
Cc: kbuild-all@01.org, axboe@kernel.dk,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] block: Don't allow illegal discard requests
Date: Wed, 4 Nov 2015 18:46:24 +0800 [thread overview]
Message-ID: <201511041823.uFo7HtIm%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446628721-11030-1-git-send-email-jack@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
Hi Jan,
[auto build test ERROR on: ext3/for_next]
[cannot apply to: v4.3 next-20151103]
url: https://github.com/0day-ci/linux/commits/Jan-Kara/block-Don-t-allow-illegal-discard-requests/20151104-172203
base: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_next
config: arm-prima2_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=arm
All errors (new ones prefixed by >>):
block/built-in.o: In function `blkdev_issue_discard':
>> block/blk-lib.c:67: undefined reference to `__aeabi_uldivmod'
>> block/blk-lib.c:67: undefined reference to `__aeabi_uldivmod'
vim +67 block/blk-lib.c
61 if (!blk_queue_discard(q))
62 return -EOPNOTSUPP;
63
64 if (q->limits.discard_granularity) {
65 unsigned int gran_sect = q->limits.discard_granularity >> 9;
66
> 67 if (sector % gran_sect || nr_sects % gran_sect)
68 return -EINVAL;
69 }
70
---
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: 12211 bytes --]
next prev parent reply other threads:[~2015-11-04 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 9:18 Jan Kara
2015-11-04 10:46 ` kbuild test robot [this message]
2015-11-04 10:48 ` kbuild test robot
2015-11-04 10:53 ` kbuild test robot
2015-11-04 11:30 ` Christoph Hellwig
2015-11-04 14:17 ` Jan Kara
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=201511041823.uFo7HtIm%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®