linux-kernel - Re: [PATCH 3/6] ktest: Reboot to good kernel after every bisect run

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: <BANLkTimtR=_X=4hWgagtRiawHH_59V7PVQ@mail.gmail.com>
Date:	Mon, 23 May 2011 17:04:17 +0200
From:	John Kacur <jkacur@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3/6] ktest: Reboot to good kernel after every bisect run

On Mon, May 23, 2011 at 3:51 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> From: Steven Rostedt <srostedt@...hat.com>
>
> Reboot after each bisect run regardless if the bisect passed
> or failed. The test may just be to boot the kernel and that kernel
> may not have a way to copy the next kerne to it. Reboot to a known
> good kernel after each bisect run.
>

How about an option to not reboot for good kernels?
--
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/