linux-kernel - dead CONFIG variables: net/bluetooth/

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

Message-ID: <Pine.LNX.4.64.0705021548050.16336@localhost.localdomain>
Date:	Wed, 2 May 2007 15:51:25 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
cc:	marcel@...tmann.org
Subject: dead CONFIG variables:  net/bluetooth/


  this example is somewhat misleading as some of the bluetooth source
(unfortunately) uses variables that start with the "CONFIG_" prefix
that have nothing to do with the Kconfig files.  for clarity, this is
the sort of thing that should be avoided.

  obviously, what's happening here is nothing but a bunch of explicit
debugging variables, but it would still be better if they were renamed
to not have that "CONFIG_" prefix (unless, of course, debugging
entries for them are added to the appropriate Kconfig files).

$ ../dead_config.sh net/bluetooth
========== BT_BNEP_DEBUG ==========
net/bluetooth/bnep/netdev.c:#ifndef CONFIG_BT_BNEP_DEBUG
net/bluetooth/bnep/sock.c:#ifndef CONFIG_BT_BNEP_DEBUG
net/bluetooth/bnep/core.c:#ifndef CONFIG_BT_BNEP_DEBUG
========== BT_CMTP_DEBUG ==========
net/bluetooth/cmtp/capi.c:#ifndef CONFIG_BT_CMTP_DEBUG
net/bluetooth/cmtp/sock.c:#ifndef CONFIG_BT_CMTP_DEBUG
net/bluetooth/cmtp/core.c:#ifndef CONFIG_BT_CMTP_DEBUG
========== BT_HCI_CORE_DEBUG ==========
net/bluetooth/hci_core.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_conn.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_event.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_sysfs.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
========== BT_HCI_SOCK_DEBUG ==========
net/bluetooth/hci_sock.c:#ifndef CONFIG_BT_HCI_SOCK_DEBUG
========== BT_HIDP_DEBUG ==========
net/bluetooth/hidp/sock.c:#ifndef CONFIG_BT_HIDP_DEBUG
net/bluetooth/hidp/core.c:#ifndef CONFIG_BT_HIDP_DEBUG
========== BT_L2CAP_DEBUG ==========
net/bluetooth/l2cap.c:#ifndef CONFIG_BT_L2CAP_DEBUG
========== BT_RFCOMM_DEBUG ==========
net/bluetooth/rfcomm/tty.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
net/bluetooth/rfcomm/sock.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
net/bluetooth/rfcomm/core.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
========== BT_SCO_DEBUG ==========
net/bluetooth/sco.c:#ifndef CONFIG_BT_SCO_DEBUG
========== BT_SOCK_DEBUG ==========
net/bluetooth/af_bluetooth.c:#ifndef CONFIG_BT_SOCK_DEBUG

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/