From: Drew DeVault <sir@cmpwn.com>
To: "Ortwin Glück" <odi@odi.ch>, "Richard Weinberger" <richard@nod.at>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Failover root devices
Date: Fri, 18 Sep 2015 11:00:17 -0400 [thread overview]
Message-ID: <55FC2701.8070300@cmpwn.com> (raw)
In-Reply-To: <55FC26B5.7080308@odi.ch>
> I personally think this is opening a can of worms. Now it's just a list
> of alternative root devices. But the kernel knows absolutely nothing
> about these. When is it fine to try an alternative? Why did the first
> one not work? Did we just not wait long enough? Or is it a failed RAID
> device? Or is it an encrypted disk that needs setup? Or is it on NFS and
> the network is not available (or we are lacking driver firmware)?
I don't think these are problems that aren't already inherent in a
single root device via root=.
> It could actually introduce security problems: if I know that a device
> will fallback to an alternative root (under my control), I can try and
> DOS the primary root.
If you have physical access then the machine is yours to do with as you
please.
--
Drew DeVault
next prev parent reply other threads:[~2015-09-18 15:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 11:40 Failover root devices Ortwin Glück
2015-09-17 11:49 ` Drew DeVault
2015-09-17 17:47 ` Richard Weinberger
2015-09-17 17:49 ` Drew DeVault
2015-09-17 17:52 ` Richard Weinberger
2015-09-17 18:05 ` Drew DeVault
2015-09-17 18:17 ` Richard Weinberger
2015-09-17 18:18 ` Drew DeVault
2015-09-17 18:19 ` Richard Weinberger
2015-09-17 18:21 ` Drew DeVault
2015-09-17 18:23 ` Richard Weinberger
2015-09-17 18:28 ` Drew DeVault
2015-09-18 14:59 ` Ortwin Glück
2015-09-18 15:00 ` Drew DeVault [this message]
2015-09-18 15:04 ` Ortwin Glück
2015-09-18 15:36 ` Austin S Hemmelgarn
2015-09-17 18:27 ` Harald Hoyer
2015-09-17 18:29 ` Drew DeVault
2015-09-17 18:33 ` Richard Weinberger
2015-09-17 18:35 ` Drew DeVault
2015-09-17 18:42 ` Richard Weinberger
2015-09-17 18:29 ` Richard Weinberger
2015-09-17 18:37 ` Austin S Hemmelgarn
2015-09-17 18:40 ` Richard Weinberger
2015-09-18 14:40 ` Austin S Hemmelgarn
-- strict thread matches above, loose matches on Subject: below --
2015-09-17 0:16 Drew DeVault
2015-09-17 16:02 ` Austin S Hemmelgarn
2015-09-17 17:30 ` Drew DeVault
2015-09-18 14:34 ` Austin S Hemmelgarn
2015-09-18 14:43 ` Drew DeVault
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=55FC2701.8070300@cmpwn.com \
--to=sir@cmpwn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=odi@odi.ch \
--cc=richard@nod.at \
/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.