linux-kernel - Re: kgdb: allow static kgdbts boot configuration

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

Message-ID: <20080421140625.GQ9554@elte.hu>
Date:	Mon, 21 Apr 2008 16:06:25 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jason Wessel <jason.wessel@...driver.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: kgdb: allow static kgdbts boot configuration


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> > +config KGDB_TESTS_ON_BOOT
> > +	bool "KGDB: Run tests on boot"
> > +	depends on KGDB_TESTS
> > +	default n
> > +	help
> > +	  Run the kgdb tests on boot up automatically without the need
> > +	  to pass in a kernel parameter
> > +
> > +config KGDB_TESTS_BOOT_STRING
> > +	string "KGDB: which internal kgdb tests to run"
> > +	depends on KGDB_TESTS_ON_BOOT
> > +	default "V1F100"
> > +	help
> > +	  This is the command string to send the kgdb test suite on
> > +	  boot.  See the drivers/misc/kgdbts.c for detailed
> > +	  information about other strings you could use beyond the
> > +	  default of V1F100.
> 
> I dunno.  Do we *really* need this feature?  I mean, if you want to 
> run the tests, you provide the boot parameter and that's it.  Adding 
> this Kconfig-time stuff on top seems excessive.

yes, i believe we really need this - this is what caught the recent 
regression in kgdb. It should all be default-off.

	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/