linux-kernel - Re: Dead Config in mm/percpu.c

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: <4C470E69.7020900@kernel.org>
Date:	Wed, 21 Jul 2010 17:12:41 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Christian Dietrich <stettberger@...ucode.de>
CC:	David Howells <dhowells@...hat.com>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: Dead Config in mm/percpu.c

On 07/21/2010 11:22 AM, Christian Dietrich wrote:
> Hi all!
>        
>         As part of the VAMOS[0] research project at the University of
> Erlangen we are looking at multiple integrity errors in linux'
> configuration system.
> 
>         I've been running a check on the mm/ sourcetree for
> config Items not defined in Kconfig and found 1 such case. Sourcecode
> blocks depending on these Items are not reachable from a vanilla
> kernel -- dead code. I've seen such dead blocks made on purpose
> e.g. while integrating new features into the kernel but generally
> they're just useless.
> 
> We found, that CONFIG_NEED_PER_CPU_KM is a dead symbol, so it isn't defined
> anywhere. Cause of that the percpu_km.c is never included anywhere. Is
> this a intended dead symbol, for use in out of tree development, or is
> this just an error?

Oh, it's new code waiting to be used.  It's for cases where SMP is
used w/o MMU.  IIRC, it was blackfin.

Thanks.

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