linux-kernel - Re: [patch] Add a simple backtrace test module

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

Date:	Thu, 10 Jan 2008 10:04:29 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch]  Add a simple backtrace test module


* Christoph Hellwig <hch@...radead.org> wrote:

> On Wed, Jan 09, 2008 at 10:42:08PM -0800, Arjan van de Ven wrote:
> > 
> > Subject: Add a simple backtrace test module
> > From: Arjan van de Ven <arjan@...ux.intel.com>
> > 
> > During the work on the x86 32 and 64 bit backtrace code I found it 
> > useful to have a simple test module to test a process and irq 
> > context backtrace. Since the existing backtrace code was buggy, I 
> > figure it might be useful to have such a test module in the kernel 
> > so that maybe we can even detect such bugs earlier..
> 
> Care to add new testcases to a new tests/ subdirectory so we can have 
> them in one place?

yeah, agreed, we'll clean this all up, and move the other testcode there 
too, ok? There's rcutorture, lock-selftests, rt-tester, 
kprobes-smoke-test and now backtracetest.

Arjan might as well want to use the opportunity and break new kernel 
namespace ground by creating the tests/ directory for the first time in 
Linux history and introduce tests/backtracetest.c :-)

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