linux-kernel - Re: [PATCH] rcu: fix section mismatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080121190851.GB32403@uranus.ravnborg.org>
Date:	Mon, 21 Jan 2008 20:08:51 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>, dipankar@...ibm.com,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH] rcu: fix section mismatch

On Mon, Jan 21, 2008 at 11:38:38AM +1100, Rusty Russell wrote:
> On Sunday 20 January 2008 08:25:49 Sam Ravnborg wrote:
> > On Sat, Jan 19, 2008 at 11:56:43AM -0800, Randy Dunlap wrote:
> > > rcu_online_cpu() should be __cpuinit instead of __devinit.
> >
> > So if we have:
> > CONFIG_HOTPLUG=n
> > CONFIG_HOTPLUG_CPU=y
> >
> > then this is a oops candidate.
> 
> At first glance, this can't happen because all CONFIG_HOTPLUG_CPU depends on 
> CONFIG_HOTPLUG or selects it, for all archs.
> 
> But CONFIG_PM_SLEEP_SMP selects CONFIG_HOTPLUG_CPU, without requiring 
> CONFIG_HOTPLUG: turning on SUSPEND or HIBERNATION does this.
For now it is a bug to select a symbol with dependencies...

If we could say that we always have HOTPLUG when we have HOTPLUG_CPU
that would kill a lot of a lot of Section Mismatch warnings.
But as things stands out we can build a kernel with HOTPLUG_CPU
but without HOTPLUG.

#if defined(CONFIG_HOTPLUG_CPU && !defined(CONFIG_HOTPLUG)
# error illegal configuration - talk to the PM guys
#endif

could do it?
 
> 
> Perhaps it's time to revisit reverse-depends for select?
Or maybe a higer level solution.
select is used for three pruposes:
- to include specific minimalitic functionality as for example done on
  the ARM Kconfig file with success
- to enable general functionality (the HAVE_* way to do it)
- to enable subsystems of different sizes

And it is only when people try to do the latter it blows up.
And they do so to make it easier for people to configure the kernel
but the end result is the opposite.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/