linux-kernel - Re: [patch 8/8] stacktrace filtering for fault-injection capabilities

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]

Message-ID: <20060920133927.GA4030@miraclelinux.com>
Date:	Wed, 20 Sep 2006 21:39:27 +0800
From:	Akinobu Mita <mita@...aclelinux.com>
To:	Don Mullis <dwm@...r.net>
Cc:	linux-kernel@...r.kernel.org, ak@...e.de, akpm@...l.org,
	Valdis.Kletnieks@...edu
Subject: Re: [patch 8/8] stacktrace filtering for fault-injection capabilities

On Tue, Sep 19, 2006 at 10:35:27AM -0700, Don Mullis wrote:
> There's no problem with hiding per se, but rather with the indentation
> level.  It's most natural for the user to have dependent options
> indented under their "parent".  For an example, in "menuconfig" try
> setting "Compile the kernel with frame unwind information";
> notice that "Stack unwind support" appears immediately underneath
> it, indented.  The indentation reminds the user why "Stack unwind
> support" has appeared.
> 

I see.

> Note that several of the pre-existing, non-fault-injection options
> under "Kernel debugging", are also broken in this way.

Perhaps you can move UNWIND_INFO, STACK_UNWIND, and DEBUG_FS
entries ealier in the list. It improves improve appearance for
other DEBUG_KERNEL dependent config options like (DEBUG_VM,
FRAME_POINTER, ...).

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