Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1171026 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2015-06-24 03:40 +0200 |
| Last post | 2015-06-25 04:00 +0200 |
| Articles | 3 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: build failure after merge of the modules tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-06-24 03:40 +0200
Re: linux-next: build failure after merge of the modules tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-06-25 01:00 +0200
Re: linux-next: build failure after merge of the modules tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-06-25 04:00 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2015-06-24 03:40 +0200 |
| Subject | linux-next: build failure after merge of the modules tree |
| Message-ID | <pEHPr-3tw-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi Rusty,
After merging the modules tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/linkage.h:4:0,
from include/linux/kernel.h:6,
from kernel/params.c:18:
kernel/params.c: In function 'param_array':
kernel/params.c:32:42: error: dereferencing pointer to incomplete type
#define KPARAM_MUTEX(mod) ((mod) ? &(mod)->param_lock : ¶m_lock)
^
include/linux/compiler.h:164:42: note: in definition of macro 'unlikely'
# define unlikely(x) __builtin_expect(!!(x), 0)
^
kernel/params.c:462:3: note: in expansion of macro 'BUG_ON'
BUG_ON(!KPARAM_IS_LOCKED(mod));
^
kernel/params.c:33:47: note: in expansion of macro 'KPARAM_MUTEX'
#define KPARAM_IS_LOCKED(mod) mutex_is_locked(KPARAM_MUTEX(mod))
^
kernel/params.c:462:11: note: in expansion of macro 'KPARAM_IS_LOCKED'
BUG_ON(!KPARAM_IS_LOCKED(mod));
^
kernel/params.c: In function 'param_array_get':
kernel/params.c:32:42: error: dereferencing pointer to incomplete type
#define KPARAM_MUTEX(mod) ((mod) ? &(mod)->param_lock : ¶m_lock)
^
include/linux/compiler.h:164:42: note: in definition of macro 'unlikely'
# define unlikely(x) __builtin_expect(!!(x), 0)
^
kernel/params.c:499:3: note: in expansion of macro 'BUG_ON'
BUG_ON(!KPARAM_IS_LOCKED(p.mod));
^
kernel/params.c:33:47: note: in expansion of macro 'KPARAM_MUTEX'
#define KPARAM_IS_LOCKED(mod) mutex_is_locked(KPARAM_MUTEX(mod))
^
kernel/params.c:499:11: note: in expansion of macro 'KPARAM_IS_LOCKED'
BUG_ON(!KPARAM_IS_LOCKED(p.mod));
^
In file included from include/linux/notifier.h:13:0,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:789,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from kernel/params.c:21:
kernel/params.c: In function 'kernel_param_lock':
kernel/params.c:32:42: error: dereferencing pointer to incomplete type
#define KPARAM_MUTEX(mod) ((mod) ? &(mod)->param_lock : ¶m_lock)
^
include/linux/mutex.h:146:44: note: in definition of macro 'mutex_lock'
#define mutex_lock(lock) mutex_lock_nested(lock, 0)
^
kernel/params.c:621:13: note: in expansion of macro 'KPARAM_MUTEX'
mutex_lock(KPARAM_MUTEX(mod));
^
kernel/params.c: In function 'kernel_param_unlock':
kernel/params.c:32:42: error: dereferencing pointer to incomplete type
#define KPARAM_MUTEX(mod) ((mod) ? &(mod)->param_lock : ¶m_lock)
^
kernel/params.c:626:15: note: in expansion of macro 'KPARAM_MUTEX'
mutex_unlock(KPARAM_MUTEX(mod));
^
Caused by commit b51d23e4e9fe ("module: add per-module param_lock").
I am not exactly sure why this fails to build. It may be an
interaction with some other change.
I have used the modules tree from next-20150623 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[toc] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2015-06-25 01:00 +0200 |
| Message-ID | <pF1Oa-6TC-13@gated-at.bofh.it> |
| In reply to | #1171026 |
[Multipart message — attachments visible in raw view] — view raw
Hi Dan, On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman <ddstreet@ieee.org> wrote: > > On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > After merging the modules tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > that's weird. Are you sure it failed during allmodconfig? I can see > why it would fail like that if CONFIG_MODULES ins't defined, which > I'll send a patch for... Pretty sure - and, in any case, I don't do any CONFIG_MODULES=n builds between tree merges (only later in the day). That is why I couldn't figure out what went wrong. I will apply your patch today and see if that helps. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2015-06-25 04:00 +0200 |
| Message-ID | <pF4Cm-2zc-9@gated-at.bofh.it> |
| In reply to | #1171731 |
[Multipart message — attachments visible in raw view] — view raw
Hi Dan, On Thu, 25 Jun 2015 08:57:06 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman <ddstreet@ieee.org> wrote: > > > > On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > After merging the modules tree, today's linux-next build (x86_64 > > > allmodconfig) failed like this: > > > > that's weird. Are you sure it failed during allmodconfig? I can see > > why it would fail like that if CONFIG_MODULES ins't defined, which > > I'll send a patch for... > > Pretty sure - and, in any case, I don't do any CONFIG_MODULES=n builds > between tree merges (only later in the day). That is why I couldn't > figure out what went wrong. > > I will apply your patch today and see if that helps. I built without your patch and it failed again, but applying your patch fixes it. Rusty, you can consider this Tested-by: Stephen Rothwell <sfr@canb.auug.org.au> for "[PATCH] modules: only use mod->param_lock if CONFIG_MODULES" -- Cheers, Stephen Rothwell sfr@canb.auug.org.au
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web