From: kbuild test robot <fengguang.wu@intel.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: kbuild-all@01.org, Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Ben Hutchings <bwh@kernel.org>
Subject: [sashal-linux-stable-security:linux-3.2.y-security 1025/1698] lib/idr.c:162:4: error: implicit declaration of function 'idr_max'
Date: Thu, 8 Sep 2016 02:17:39 +0800 [thread overview]
Message-ID: <201609080237.wVcP7RD3%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable-security.git linux-3.2.y-security
head: 898614808b51d26adab360afbbbc5b501abdf962
commit: 71d417302c0d4ea1341902c88218769ab91e28e8 [1025/1698] idr: fix overflow bug during maximum ID calculation at maximum height
config: i386-randconfig-s0-201636 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
git checkout 71d417302c0d4ea1341902c88218769ab91e28e8
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
lib/idr.c: In function 'sub_alloc':
>> lib/idr.c:162:4: error: implicit declaration of function 'idr_max' [-Werror=implicit-function-declaration]
if (id > idr_max(idp->layers)) {
^
cc1: some warnings being treated as errors
vim +/idr_max +162 lib/idr.c
156 /* no space available go back to previous layer. */
157 l++;
158 oid = id;
159 id = (id | ((1 << (IDR_BITS * l)) - 1)) + 1;
160
161 /* if already at the top layer, we need to grow */
> 162 if (id > idr_max(idp->layers)) {
163 *starting_id = id;
164 return IDR_NEED_TO_GROW;
165 }
---
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: 14333 bytes --]
reply other threads:[~2016-09-07 23:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201609080237.wVcP7RD3%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bwh@kernel.org \
--cc=kbuild-all@01.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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