From: Helen Koike <helen.koike@collabora.com>
To: dm-devel@redhat.com
Cc: wad@chromium.org, snitzer@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-lvm@redhat.com,
enric.balletbo@collabora.com, kernel@collabora.com,
agk@redhat.com
Subject: Re: [linux-lvm] [PATCH 0/2] boot to a mapped device
Date: Wed, 26 Sep 2018 02:02:25 -0300 [thread overview]
Message-ID: <610d5f5e-ea07-631d-04d3-18fd3da0fe2a@collabora.com> (raw)
In-Reply-To: <cover.1537936397.git.helen.koike@collabora.com>
On 9/26/18 2:00 AM, Helen Koike wrote:
> This series is reviving an old patchwork.
> Booting from a mapped device requires an initramfs. This series is
> allows for device-mapper targets to be configured at boot time for
> use early in the boot process (as the root device or otherwise).
>
> Example, the following could be added in the boot parameters.
> dm="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
>
> Enric Balletbo i Serra (1):
> dm ioctl: add a device mapper ioctl function.
>
> Will Drewry (1):
> init: add support to directly boot to a mapped device
>
> .../admin-guide/kernel-parameters.rst | 1 +
> .../admin-guide/kernel-parameters.txt | 3 +
> Documentation/device-mapper/dm-boot.txt | 63 +++
> drivers/md/dm-ioctl.c | 50 ++
> include/linux/device-mapper.h | 6 +
> init/Makefile | 1 +
> init/do_mounts.c | 1 +
> init/do_mounts.h | 10 +
> init/do_mounts_dm.c | 475 ++++++++++++++++++
> 9 files changed, 610 insertions(+)
> create mode 100644 Documentation/device-mapper/dm-boot.txt
> create mode 100644 init/do_mounts_dm.c
>
Sorry about sending this email multiple times, my git send-email wans't
properly configured.
Helen
next prev parent reply other threads:[~2018-09-26 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 5:00 [linux-lvm] [PATCH 0/2] boot to a mapped device Helen Koike
2018-09-26 5:00 ` [linux-lvm] [PATCH 1/2] dm ioctl: add a device mapper ioctl function Helen Koike
2018-09-26 5:00 ` [linux-lvm] [PATCH 2/2] init: add support to directly boot to a mapped device Helen Koike
2018-09-26 16:09 ` Randy Dunlap
2018-09-26 5:02 ` Helen Koike [this message]
2018-09-26 7:16 ` [linux-lvm] [PATCH 0/2] " Richard Weinberger
2018-09-27 14:23 ` Mike Snitzer
2018-09-27 16:36 ` Kees Cook
2018-09-27 18:31 ` Mike Snitzer
2018-10-19 16:27 ` Helen Koike
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=610d5f5e-ea07-631d-04d3-18fd3da0fe2a@collabora.com \
--to=helen.koike@collabora.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=enric.balletbo@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=snitzer@redhat.com \
--cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).