linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <861vaxjij8.fsf@peer.zerties.org>
Date:	Wed, 21 Jul 2010 11:22:51 +0200
From:	Christian Dietrich <stettberger@...ucode.de>
To:	Tejun Heo <tj@...nel.org>, David Howells <dhowells@...hat.com>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Dead Config in mm/percpu.c

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?

Regards
        Christian Dietrich
-- 
(λ x . x x) (λ x . x x) -- See how beatiful the lambda is
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
--
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/