From: kbuild test robot <lkp@intel.com>
To: Weilong Chen <chenweilong@huawei.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
jcm@jonmasters.org, rusty@rustcorp.com.au
Subject: Re: [PATCH] Race between cat /proc/kallsyms and rmmod
Date: Sat, 30 Jan 2016 18:45:33 +0800 [thread overview]
Message-ID: <201601301840.Xfu68uAO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454149416-105680-1-git-send-email-chenweilong@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
Hi Weilong,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160129]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Weilong-Chen/Race-between-cat-proc-kallsyms-and-rmmod/20160130-182606
config: i386-randconfig-a0-201604 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/notifier.h:13:0,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:728,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from kernel/kallsyms.c:15:
kernel/kallsyms.c: In function 's_start':
>> kernel/kallsyms.c:519:14: error: 'module_mutex' undeclared (first use in this function)
mutex_lock(&module_mutex);
^
include/linux/mutex.h:146:44: note: in definition of macro 'mutex_lock'
#define mutex_lock(lock) mutex_lock_nested(lock, 0)
^
kernel/kallsyms.c:519:14: note: each undeclared identifier is reported only once for each function it appears in
mutex_lock(&module_mutex);
^
include/linux/mutex.h:146:44: note: in definition of macro 'mutex_lock'
#define mutex_lock(lock) mutex_lock_nested(lock, 0)
^
kernel/kallsyms.c: In function 's_stop':
kernel/kallsyms.c:527:16: error: 'module_mutex' undeclared (first use in this function)
mutex_unlock(&module_mutex);
^
vim +/module_mutex +519 kernel/kallsyms.c
513 return NULL;
514 return p;
515 }
516
517 static void *s_start(struct seq_file *m, loff_t *pos)
518 {
> 519 mutex_lock(&module_mutex);
520 if (!update_iter(m->private, *pos))
521 return NULL;
522 return m->private;
---
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: 25004 bytes --]
next prev parent reply other threads:[~2016-01-30 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 10:23 Weilong Chen
2016-01-30 10:45 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 11:13 Alexey Dobriyan
2007-03-14 12:11 ` Andi Kleen
2007-03-14 12:55 ` Paulo Marques
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=201601301840.Xfu68uAO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chenweilong@huawei.com \
--cc=jcm@jonmasters.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®