linux-kernel - Re: [RFC] Linux Kernel Dump 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:	Fri, 8 Sep 2006 02:35:19 +0530
From:	Maneesh Soni <maneesh@...ibm.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	ankita@...ibm.com, linux-kernel@...r.kernel.org,
	fernando@....ntt.co.jp
Subject: Re: [RFC] Linux Kernel Dump Test Module

On Thu, Sep 07, 2006 at 01:48:50PM -0700, Andrew Morton wrote:
> On Thu, 7 Sep 2006 19:23:29 +0530
> Ankita Garg <ankita@...ibm.com> wrote:
> 
> > Please find below a patch for a simple module to test Linux Kernel Dump 
> > mechanism. This module uses jprobes to install/activate pre-defined crash
> > points. At different crash points, various types of crashing scenarios 
> > are created like a BUG(), panic(), exception, recursive loop and stack 
> > overflow. The user can activate a crash point with specific type by
> > providing parameters at the time of module insertion. Please see the file
> > header for usage information. The module is based on the Linux Kernel
> > Dump Test Tool by Fernando <http://lkdtt.sourceforge.net>.
> > 
> > This module could be merged with mainline. Jprobes is used here so that the 
> > context in which crash point is hit, could be maintained. This implements
> > all the crash points as done by LKDTT except the one in the middle of 
> > tasklet_action(). 
> 
> "could be merged with mainline": why "could"?  What would be the
> disadvantages of doing this?
> 
I don't see disadvantages, probably the usefulness is in doubt.

> I think having test code like this in mainline is a good idea, particularly
> for a subsystem like [kj]probes.
> 
Do you mean using [kj]probes? 

> It's a bit regrettable that the code "knows" about particular not-exported,
> arch-specific core kernel functions, but I guess those don't change very
> often, so we won't be forever patching this module.
> 
Probes at the beginning of the routine instead of at some offset (the
way it is already done), should reduce the rework burdon.

The crashpoints are in core kernel internal routines but I donot see 
any "arch-specific" functions selected. I think the module can be used for 
any architecture with jprobe support.

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