public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Helge Deller <deller@gmx.de>
Subject: Re: modules: Fix build error in the !CONFIG_KALLSYMS case
Date: Fri, 28 Aug 2009 21:41:30 +0930	[thread overview]
Message-ID: <200908282141.31175.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090828084456.GB3454@elte.hu>

On Fri, 28 Aug 2009 06:14:56 pm Ingo Molnar wrote:
> 
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > James Bottomley (1):
> >       module: workaround duplicate section names
> 
> -tip testing found that this patch breaks the build on x86 if 
> CONFIG_KALLSYMS is disabled:
> 
>  kernel/module.c: In function ‘load_module’:
>  kernel/module.c:2367: error: ‘struct module’ has no member named ‘sect_attrs’
>  distcc[8269] ERROR: compile kernel/module.c on ph/32 failed
>  make[1]: *** [kernel/module.o] Error 1
>  make: *** [kernel] Error 2
>  make: *** Waiting for unfinished jobs....
> 
> Commit 1b364bf misses the fact that section attributes are only 
> built and dealt with if kallsyms is enabled. The patch below fixes 
> this.
> 
> ( note, technically speaking this should depend on CONFIG_SYSFS as
>   well but this patch is correct too and keeps the #ifdef less
>   intrusive - in the KALLSYMS && !SYSFS case the code is a NOP. )
> 
> Signed-off-by: Ingo Molnar <mingo@elte.hu>

Acked-by: Rusty Russell <rusty@rustcorp.com.au>

Thanks,
Rusty.

  parent reply	other threads:[~2009-08-28 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  1:24 Linux 2.6.31-rc8 Linus Torvalds
2009-08-28  8:22 ` Arnd Hannemann
2009-08-28  8:35   ` Ingo Molnar
2009-08-28  8:44 ` modules: Fix build error in the !CONFIG_KALLSYMS case Ingo Molnar
2009-08-28  9:24   ` Amerigo Wang
2009-08-28 12:07   ` James Bottomley
2009-08-28 12:14     ` Ingo Molnar
2009-08-28 12:11   ` Rusty Russell [this message]
2009-08-28 16:58 ` Linux 2.6.31-rc8 Eric Paris
2009-08-28 22:48 ` Alejandro Riveira Fernández

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=200908282141.31175.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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