| 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
| ||
|
Message-ID: <468E833C.6030300@redhat.com> Date: Fri, 06 Jul 2007 14:00:28 -0400 From: Chuck Ebbert <cebbert@...hat.com> To: Clemens Koller <clemens.koller@...gramm.de> CC: Bodo Eggert <7eggert@....de>, linux-kernel@...r.kernel.org Subject: Re: [RFC][PATCH] introduce panic_gently On 07/06/2007 03:57 AM, Clemens Koller wrote: > Bodo Eggert schrieb: >> If the boot process failes to find init or the root fs, the cause has >> usually scrolled off the screen, and because of the panic, it can't be >> reached anymore. >> >> This patch introduces panic_gently, which will allow to use the >> scrollback buffer and to reboot, but it can't be called from unsafe >> context. > > In the case where you introduced panic_gently() there is IMHO no reason > to panic() at all. There is no bug which got hit, the machine just needs > user intervention because of wrong boot parameters (in most cases). > > What about asking the user for the correct root= or init= parameters > and just retry/continue the boot process? > > The 180seconds reboot timeout also doesn't make sense here. The problem > won't go away after a reboot without user interaction. What about GRUB fallbacks? The fallback image/kernel will start automatically on reboot if you use that feature. - 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/
Powered by blists - more mailing lists