linux-kernel - Re: [PATCH] padata: section cleanup

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]

Date:	Wed, 31 Mar 2010 14:58:17 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Henrik Kretzschmar <henne@...htwindheim.de>,
	steffen.klassert@...unet.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] padata: section cleanup

On Mon, 29 Mar 2010 16:15:50 +0800
Herbert Xu <herbert@...dor.apana.org.au> wrote:

> On Sat, Mar 27, 2010 at 07:53:46AM +0100, Henrik Kretzschmar wrote:
> > This patch removes the __cupinit from padata_cpu_callback(),
> > which is refered by the exportet function padata_alloc().
> > 
> > This could lead to problems if CONFIG_HOTPLUG_CPU is disabled,
> > which should happen very often.
> > 
> > WARNING: kernel/built-in.o(.text+0x7ffcb): Section mismatch in reference from the function padata_alloc() to the function .cpuinit.text:padata_cpu_callback()
> > The function padata_alloc() references
> > the function __cpuinit padata_cpu_callback().
> > This is often because padata_alloc lacks a __cpuinit
> > annotation or the annotation of padata_cpu_callback is wrong.
> > 
> > Signed-off-by: Henrik Kretzschmar <henne@...htwindheim.de>
> 
> Patch applied.  Thanks!

(wtf?)

OK, on behalf of thousands I ask: what the heck is kernel/padata.c? 

Seems to have popped up in 2.6.34, positioned as generic kernel-wide
code only it has been secreted away on the linux-crypto list.  Please
don't do this.

What is it for, how does it work, where might it otherwise be used,
what are the dynamics, why does it use softirqs rather than (say)
kernel threads and how do we stop it from using yield()?

--
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/