Date: Thu, 26 Nov 2015 15:45:59 +0100
From: Valentin Rothberg <valentinrothberg@gmail.com>
To: chris@chris-wilson.co.uk
Cc: mingo@kernel.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
        Patrick Plagwitz <patrick.plagwitz@fau.de>,
        Andreas Ziegler <ziegler@cs.fau.de>, Daniel Lohmann <dl@cs.fau.de>
Subject: kernel: stop_machine: report (un)dead code (and feedback request)
Message-ID: <20151126144559.GA19758@debian-vm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1964
Lines: 45

Hi Chris,

your commit 4c477de14237 ("kernel: remove stop_machine() Kconfig
dependency") has shown up in today's linux-next tree (20151126).
The commit changes the #ifdef condition in kernel/stop_machine.c
from/to:

    -#if defined(CONFIG_STOP_MACHINE) && defined(CONFIG_SMP)
    +#if defined(CONFIG_SMP) || defined(CONFIG_HOTPLUG_CPU)

Although this change fixes certain configs on X86, the condition now is
a tautology since CONFIG_SMP is already required to compile the file:

    kernel/Makefile:65:obj-$(CONFIG_SMP) += stop_machine.o

AFAIU, we can safely remove this #ifdef?

I detected this issue with undertaker-checkpatch [1].  We're a research
group at the University of Erlangen-Nuremberg, running daily checks on
linux-next to report Kconfig related issues, such as dead and undead
code, or references on undefined symbols.

One of the students, Patrick, who writes his Bachelor's thesis in our
group implemented a web-framework to visualize kernel code w.r.t. CPP
#ifdef statements and the bugs our tools [1] detect.  You can find the
visualization of the mentioned issue at [2].  The description of the
tautology in the #ifdef condition can be found by clicking on the
'details' menu of the block.

We'll be happy to receive any kind of feedback of the recipients of this
mail.  Do you like/dislike the visualization?  Does it help you to
understand the described issue? etc.  The main purpose of the framework
is to aid when sending reports.  It's much easier and nicer to point to
a website visualizing a problem than just describing it textually.

Kind regards,
 Valentin

[1] https://undertaker.cs.fau.de
[2] http://cados.cs.fau.de:4567/4c477de14237193c99329ca82965c1211b4ee81e/kernel/stop_machine.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/