mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
To: David Howells <dhowells@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Andreas Dilger <adilger@dilger.ca>, Jiri Kosina <jkosina@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Stultz <johnstul@us.ibm.com>, Tejun Heo <tj@kernel.org>,
	linux-kernel@vger.kernel.org
Cc: vamos-dev@i4.informatik.uni-erlangen.de
Subject: [PATCH 0/4] Removing dead code
Date: Tue, 10 Aug 2010 11:11:02 +0200	[thread overview]
Message-ID: <cover.1281431005.git.qy03fugy@stud.informatik.uni-erlangen.de> (raw)

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 arch/frv sourcetree for
config Items not defined in Kconfig and found 4 such cases. 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.

        Each of the patches in this patchset removes on such dead
config Item, I'd be glad if you consider applying them. I've been
doing deeper analysis of such issues before and can do so again but
I'm not so sure they were fastly usefull.


I wasn't able to build a vanilla kernel allyesconfig, therefore these
patches might break something. But because they are just removing dead
code it is unlikely.

Another problem i encountered was CONFIG_PREEMPT, which isn't
selectable in frv Kconfig because it doesn include
kernel/Kconfig.preempt. But there ist plenty of evidence for me, that
there is preemption support in frv.


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

Regards

        Christian Dietrich

[0] http://vamos1.informatik.uni-erlangen.de/

Christian Dietrich (4):
  arch/frv: Removing dead RAMKERNEL config option
  arch/frv: Removing dead HEARTBEAT config option
  arch/frv: Removing dead NO_KERNEL_MSG config option
  arch/frv: Removing dead DEBUG_STACK_USAGE config option

 arch/frv/include/asm/bug.h         |    4 ----
 arch/frv/include/asm/thread_info.h |   11 -----------
 arch/frv/kernel/debug-stub.c       |    2 --
 arch/frv/kernel/time.c             |    6 ------
 arch/frv/mm/init.c                 |   17 -----------------
 5 files changed, 0 insertions(+), 40 deletions(-)


             reply	other threads:[~2010-08-10  9:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10  9:11 Christian Dietrich [this message]
2010-08-10  9:11 ` [PATCH 1/4] arch/frv: Removing dead RAMKERNEL config option Christian Dietrich
2010-08-10  9:37   ` Felipe Balbi
2010-08-10 10:54     ` Christian Dietrich
2010-08-10 11:54       ` Felipe Balbi
2010-08-10  9:11 ` [PATCH 2/4] arch/frv: Removing dead HEARTBEAT " Christian Dietrich
2010-08-10  9:35   ` Felipe Balbi
2010-08-10 11:06     ` Christian Dietrich
2010-08-10  9:11 ` [PATCH 3/4] arch/frv: Removing dead NO_KERNEL_MSG " Christian Dietrich
2010-08-10  9:11 ` [PATCH 4/4] arch/frv: Removing dead DEBUG_STACK_USAGE " Christian Dietrich
  -- strict thread matches above, loose matches on Subject: below --
2010-07-14 13:21 [PATCH 0/4] Removing dead code Christian Dietrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1281431005.git.qy03fugy@stud.informatik.uni-erlangen.de \
    --to=qy03fugy@stud.informatik.uni-erlangen.de \
    --cc=adilger@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=johnstul@us.ibm.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=vamos-dev@i4.informatik.uni-erlangen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®