linux-kernel - Re: [PATCH 0/2] boot to a mapped device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFLxGvzCDOTR4stPmp1TTLkQ39x3e8MQuL=AR754abKc5skhpA@mail.gmail.com>
Date:   Wed, 26 Sep 2018 09:16:57 +0200
From:   Richard Weinberger <richard.weinberger@...il.com>
To:     helen.koike@...labora.com
Cc:     device-mapper development <dm-devel@...hat.com>, agk@...hat.com,
        snitzer@...hat.com, LKML <linux-kernel@...r.kernel.org>,
        enric.balletbo@...labora.com, Will Drewry <wad@...omium.org>,
        linux-doc@...r.kernel.org, linux-lvm@...hat.com,
        kernel@...labora.com
Subject: Re: [PATCH 0/2] boot to a mapped device

Helen,

On Wed, Sep 26, 2018 at 7:01 AM Helen Koike <helen.koike@...labora.com> 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).

What is the reason for this patch series?
Setting up non-trivial root filesystems/storage always requires an
initramfs, there is nothing
wrong about this.

> 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

Hmmm, the new dm= parameter is anything but easy to get right.

-- 
Thanks,
//richard