From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] check shm mount succeeded in shmem_file_setup
Date: Sat, 20 Jul 2002 14:19:39 +1000 [thread overview]
Message-ID: <20020720043607.090A241AC@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 19 Jul 2002 10:02:21 EST." <200207191502.KAA02022@ccure.karaya.com>
In message <200207191502.KAA02022@ccure.karaya.com> you write:
> rusty@rustcorp.com.au said:
> > And if the initialization fails at boot, we're screwed anyway.
>
> Why? If it fails, it still boots fine until something tries using shared
> memory. With UML and my Debian fs, that's Apache, which is the last thing
> before the gettys run.
Same argument applies to lots of subsystems, but I'd suggest a policy:
we should be failing the boot rather than coming partially up and
trying to deal with failures that shouldn't happen.
Unfortunately, we don't check init returns at boot, because we
*expect* device driver initialization to fail for builtin device
drivers who have found no device. It'd be nice to standardize on
-ENODEV for these failures, so we *could* handle these failures
easily, and discourage the current sloppiness.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-07-20 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207190354.WAA05241@ccure.karaya.com>
2002-07-19 7:53 ` [PATCH] check shm mount succeeded in shmem_file_setup Rusty Russell
2002-07-19 15:02 ` Jeff Dike
2002-07-20 4:19 ` Rusty Russell [this message]
2002-07-11 5:48 ` Jeff Dike
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=20020720043607.090A241AC@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox