linux-kernel - [RFC PATCH 0/8] gcov kernel support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <480C89BD.8080909@de.ibm.com>
Date:	Mon, 21 Apr 2008 14:34:05 +0200
From:	Peter Oberparleiter <peter.oberparleiter@...ibm.com>
To:	linux-kernel@...r.kernel.org
CC:	ltp-list@...ts.sourceforge.net, ltp-coverage@...ts.sourceforge.net,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [RFC PATCH 0/8] gcov kernel support

This set of patches enables the use of GCC's coverage testing tool
gcov [1] with kernel 2.6.25. Coverage data for the running kernel is
exported via debugfs in a gcov-compatible format. To get coverage
data for a specific file, simply use gcov with the -o option:

# gcov -o /sys/kernel/debug/gcov/tmp/linux-2.6.25/kernel spinlock.c

This will create source code files annotated with execution counts
in the current directory. In addition, graphical gcov front-ends such
as lcov [2] can be used to automate the process of collecting data
for the entire kernel and provide coverage overviews in HTML format.

Possible uses:

* debugging (has this line been executed at all?)
* test improvement (how do I change my test to cover these lines?)
* minimizing kernel configurations (do I need this option if the
  associated code is never executed?)

Patch overview:

[patch 1/8] kernel: call constructors
[patch 2/8] kbuild: let addtree result in absolute paths only
[patch 3/8] kbuild: convert include and source paths
[patch 4/8] module: add MODULE_STATE_GOING notifier call
[patch 5/8] module: add function to map address to containing module
[patch 6/8] seq_file: add function to write binary data
[patch 7/8] gcov: add gcov profiling infrastructure
[patch 8/8] gcov: architecture specific compile flag adjustments

Patches 1-6 introduce/change functionality required for gcov's
profiling mechanism to work. Patch 7 implements the actual gcov
support and debugfs interface. Patch 8 is required for architecture
specific adjustments.

Known issues:

* some architecture specific problems: the patch has been tested
  successfully on s390 and i386. Known problems exist on x86_64 and
  arm (to be investigated)
* GCC's profiling mechanism together with optimization sometimes
  produces skewed data (see [1])
* GCC's profiling code assumes single-threaded execution
* gcov assumes that a program has finished when coverage data is
  analyzed

Despite these issues, the data which can be obtained has been proven
to be sufficiently accurate for most practical uses.

History:

Hubertus Franke <frankeh@...ibm.com> wrote the first version of this
patch around 2002. Since then it has been adapted to new versions of
the kernel and GCC with contributions by several people (see file
kernel/gcov/fs.c, write me if I missed anyone). Due to regular
requests, I rewrote the gcov-kernel patch from scratch so that it
would (hopefully) be fit for inclusion into the upstream kernel.

--
[1] http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
[2] http://ltp.sourceforge.net/coverage/lcov.php

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