From: Kees Cook <keescook@chromium.org>
To: Alasdair Kergon <agk@redhat.com>
Cc: Kees Cook <keescook@chromium.org>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, Jonathan Corbet <corbet@lwn.net>,
Shaohua Li <shli@kernel.org>,
Dan Ehrenberg <dehrenberg@chromium.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Chen Yu <yu.c.chen@intel.com>,
Vishnu Pratap Singh <vishnu.ps@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yaowei Bai <baiyaowei@cmss.chinamobile.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, Will Drewry <wad@chromium.org>,
David Zeuthen <zeuthen@google.com>
Subject: [PATCH v5 0/3] init: add support to directly boot to a mapped device
Date: Sat, 20 Feb 2016 10:13:49 -0800 [thread overview]
Message-ID: <1455992032-14594-1-git-send-email-keescook@chromium.org> (raw)
This is a resurrection of a patch series from a few years back, first
brought to the dm maintainers in 2010. It creates a way to define dm
devices on the kernel command line for systems that do not use an
initramfs, or otherwise need a dm running before init starts.
This has been used by Chrome OS for several years, and now by Brillo
(and likely Android soon).
The last version was v4:
https://patchwork.kernel.org/patch/104860/
https://patchwork.kernel.org/patch/104861/
-Kees
next reply other threads:[~2016-02-20 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 18:13 Kees Cook [this message]
2016-02-20 18:13 ` [PATCH v5 1/3] dm: export a table+mapped device to the ioctl interface Kees Cook
2016-02-20 18:13 ` [PATCH v5 2/3] dm: make mapped_device locking functions available Kees Cook
2016-02-20 18:13 ` [PATCH v5 3/3] init: add support to directly boot to a mapped device Kees Cook
2016-02-21 22:08 ` [PATCH v5 0/3] " Alasdair G Kergon
2016-02-22 18:55 ` Kees Cook
2016-02-26 16:53 ` Mike Snitzer
2016-02-26 18:52 ` Kees Cook
2016-02-26 19:21 ` Mike Snitzer
2016-02-26 19:59 ` Kees Cook
2016-02-26 20:47 ` Mike Snitzer
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=1455992032-14594-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=corbet@lwn.net \
--cc=dehrenberg@chromium.org \
--cc=dm-devel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
--cc=vishnu.ps@samsung.com \
--cc=wad@chromium.org \
--cc=yu.c.chen@intel.com \
--cc=zeuthen@google.com \
/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;
as well as URLs for NNTP newsgroup(s).