linux-kernel - Re: [RFC][PATCH] Make prepare

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: <20070514160403.6414f149@dhcp-252-105.norway.atmel.com>
Date:	Mon, 14 May 2007 16:04:03 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Al Viro <viro@....linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] Make prepare_namespace() wait for devices

On Mon, 14 May 2007 15:56:15 +0200
Pierre Ossman <drzeus-list@...eus.cx> wrote:

> > As for the patch, an infinite loop is *much* worse than a panic.
> > When one is installing a new kernel on remote box, having it
> > booted with reboot on panic and loader falling back to old
> > kernel on the next boot is a bloody good idea - gives you extra
> > safety.  With your patch it will get the box stuck.
> >     
> 
> Ok. So a timeout or having the entire thing Kconfig optional?

How about command-line optional?

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