From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [RFC][PATCH] Make prepare_namespace() wait for devices
Date: Mon, 14 May 2007 15:56:15 +0200 [thread overview]
Message-ID: <46486A7F.8050705@drzeus.cx> (raw)
In-Reply-To: <20070514123436.GB4095@ftp.linux.org.uk>
Al Viro wrote:
> On Mon, May 14, 2007 at 02:19:37PM +0200, Pierre Ossman wrote:
>
> First of all, please do not put patches in attachments.
>
>
My mailer tends to fsck them up if I just paste them. And it's attached
without any base64 silliness, so most people can usually read it directly.
> 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?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-05-14 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 12:19 [RFC][PATCH] Make prepare_namespace() wait for devices Pierre Ossman
2007-05-14 12:34 ` Al Viro
2007-05-14 13:56 ` Pierre Ossman [this message]
2007-05-14 14:04 ` Haavard Skinnemoen
2007-05-14 15:18 ` [RFC][PATCH] Make prepare_namespace() wait for devices (v2) Pierre Ossman
2007-05-16 9:15 ` Haavard Skinnemoen
2007-05-16 12:31 ` Ben Nizette
2007-05-18 17:55 ` [RFC][PATCH] Make prepare_namespace() wait for devices Andi Kleen
2007-05-18 17:09 ` Pierre Ossman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46486A7F.8050705@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.