From: Christoph Egger <siccegge@cs.fau.de>
To: Jeff Dike <jdike@addtoit.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: vamos-dev@i4.informatik.uni-erlangen.de
Subject: [PATCH 0/3] Removing dead code
Date: Thu, 29 Jul 2010 17:28:40 +0200 [thread overview]
Message-ID: <cover.1280417117.git.siccegge@cs.fau.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/um sourcetree for config
Items not defined in Kconfig and found 10 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 build the patches against a vanilla kernel in order to
try if the kernel compiles with this patches. As reported earlier
today the build currently fails for plain um but adding this patchset
doesn't change the failing in any way. That was a i386 build.
Please keep me informed of this patch getting confirmed /
merged so we can keep track of it.
Regards
Christoph Egger
[0] http://vamos1.informatik.uni-erlangen.de/
Christoph Egger (3):
Removing dead PROC_MM
Removing conditionalizing containing exactly the same code
Removing dead copy&paste code
arch/um/kernel/ptrace.c | 21 ---------------------
arch/um/sys-i386/asm/archparam.h | 4 ----
arch/um/sys-i386/shared/sysdep/system.h | 11 +----------
arch/um/sys-ppc/misc.S | 6 ------
arch/um/sys-ppc/shared/sysdep/ptrace.h | 5 +----
arch/um/sys-x86_64/shared/sysdep/system.h | 10 +---------
6 files changed, 3 insertions(+), 54 deletions(-)
next reply other threads:[~2010-07-29 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 15:28 Christoph Egger [this message]
2010-07-29 15:28 ` [PATCH 1/3] Removing dead PROC_MM Christoph Egger
2010-07-29 15:29 ` [PATCH 2/3] Removing conditionalizing containing exactly the same code Christoph Egger
2010-07-29 15:29 ` [PATCH 3/3] Removing dead copy&paste code Christoph Egger
-- strict thread matches above, loose matches on Subject: below --
2010-07-21 12:34 [PATCH 0/3] Removing dead code Christian Dietrich
2010-07-14 11:31 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.1280417117.git.siccegge@cs.fau.de \
--to=siccegge@cs.fau.de \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--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