linux-kernel - Unreferenced config in kernel (libata-sff.c) source (NO_ATA

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: <20100120142943.GE3580@faui49.informatik.uni-erlangen.de>
Date:	Wed, 20 Jan 2010 15:29:43 +0100
From:	Christoph Egger <siccegge@...d.informatik.uni-erlangen.de>
To:	linux-kernel@...r.kernel.org, htejun@...il.com,
	linux-ide@...r.kernel.org, jgarzik@...ox.com
Cc:	siccegge@...d.informatik.uni-erlangen.de,
	Reinhard.Tartler@...ormatik.uni-erlangen.de
Subject: Unreferenced config in kernel (libata-sff.c) source (NO_ATA_LEGACY)

Hi all!

	As part of the VAMOS[0] research project at the University of
Erlangen we're checking referential integrity between kernel KConfig
options and in-code Conditional blocks.

./drivers/ata/libata-sff.c:2948:#if defined(CONFIG_NO_ATA_LEGACY)

	That's the only place where it is checked for
NO_ATA_LEGACY. As this Item does appear nowhere in KConfig and
therefor is not selectable I'm wondering whether that small Code
fragment should be dropped or a new KConfig option should be added?

	Please keep me informed of this patch getting confirmed /
merged so we can keep track of it.

Regards

	Christoph Egger

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