[PATCH] Documentation/dm-init: fix multi device example

2019-06-04 Thread Helen Koike
The example in the docs regarding multiple device-mappers is invalid (it has a wrong number of arguments), it's a left over from previous versions of the patch. Replace the example with an valid and tested one. Signed-off-by: Helen Koike --- Documentation/device-mapper/dm-init.txt | 14

Re: [PATCH v12] dm: add support to directly boot to a mapped device

2019-06-04 Thread Helen Koike
Hi Stephen, On 6/3/19 8:02 PM, Stephen Boyd wrote: > Quoting Helen Koike (2019-02-21 12:33:34) >> Add a "create" module parameter, which allows device-mapper targets to be >> configured at boot time. This enables early use of dm targets in the boot >> process (

[PATCH v2] dm ioctl: fix hang in early create error condition

2019-05-15 Thread Helen Koike
cess. Fix this by calling __hash_remove() in the error path. Fixes: 6bbc923dfcf57d ("dm: add support to directly boot to a mapped device") Cc: sta...@vger.kernel.org Signed-off-by: Helen Koike --- Hi, I also tested this patch version with the new test case in the following

Re: dm ioctl: fix hang in early create error condition

2019-05-15 Thread Helen Koike
Hi, On 5/13/19 10:37 PM, Mike Snitzer wrote: > On Mon, May 13 2019 at 3:25P -0400, > Helen Koike wrote: > >> The dm_early_create() function (which deals with "dm-mod.create=" kernel >> command line option) calls dm_hash_insert() who gets an extra reference >

[PATCH] dm ioctl: fix hang in early create error condition

2019-05-13 Thread Helen Koike
cess. Fix this by calling __hash_remove() in the error path. Fixes: 6bbc923dfcf57d ("dm: add support to directly boot to a mapped device") Cc: sta...@vger.kernel.org Signed-off-by: Helen Koike --- Hi, I tested this patch by adding a new test case in the following test script: https://

[dm-devel] [PATCH] dm: init: fix max devices/targets checks

2019-04-26 Thread Helen Koike
dm-init should allow up to DM_MAX_{DEVICES,TARGETS} for devices/targets, and not DM_MAX_{DEVICES,TARGETS} - 1. Fix the checks and also fix the error message when the number of devices is surpassed. Signed-off-by: Helen Koike --- Hi, This patch was tested by manipulating DM_MAX_TARGETS

[dm-devel] [PATCH v12] dm: add support to directly boot to a mapped device

2019-02-22 Thread Helen Koike
ser makes a mistake, choosing the wrong device to be the mirror or the cache can corrupt data. The only targets allowed are: * crypt * delay * linear * snapshot-origin * striped * verity Co-developed-by: Will Drewry Co-developed-by: Kees Cook Co-developed-by: Enric Balletbo i Serra Signed-off-by: He

[dm-devel] [PATCH v11] dm: add support to directly boot to a mapped device

2019-02-22 Thread Helen Koike
Serra [refactored for upstream] Signed-off-by: Helen Koike --- Hello, As mentioned in previous discussions, the need to create an initramfs adds another layer of complexity when performing tests or preparing a BSP for a board. Taking care of initramfs is always a bit painful, it also occupies space

[dm-devel] [PATCH v10 1/2] dm ioctl: add a device mapper ioctl function.

2018-11-02 Thread Helen Koike
From: Enric Balletbo i Serra Add a dm_ioctl_cmd to issue the equivalent of a DM ioctl call in kernel. Signed-off-by: Enric Balletbo i Serra --- Changes since v9: - https://www.redhat.com/archives/linux-lvm/2018-September/msg00016.html - Reorganize variables --- drivers/md/dm-ioctl.c

[dm-devel] [PATCH v10 0/2] dm: boot a mapped device without an initramfs

2018-11-02 Thread Helen Koike
As mentioned in the discussion from the previous version of this patch, Android and Chrome OS do not use initramfs mostly due to boot time and size liability. A practical example as mentioned by Kees is that Chrome OS has a limited amount of storage available for the boot image as it is covered by

[dm-devel] [PATCH v10 2/2] init: add support to directly boot to a mapped device

2018-11-02 Thread Helen Koike
Serra [rework to use concise format | rework for upstream] Signed-off-by: Helen Koike --- Hello, In this patch, I constrained the targets allowed to be used by dm=, but I am not entirely familiar with all the targets. I blacklisted the ones mentioned previously and some other that I think

Re: [dm-devel] [PATCH 0/2] boot to a mapped device

2018-10-19 Thread Helen Koike
Weinberger wrote: >>> >>>> Helen, >>>> >>>> On Wed, Sep 26, 2018 at 7:01 AM Helen Koike >>>> wrote: >>>>> >>>>> This series is reviving an old patchwork. >>>>> Booting from a mapped device requires an

Re: [dm-devel] [PATCH 0/2] boot to a mapped device

2018-09-25 Thread Helen Koike
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

[dm-devel] [PATCH 1/2] dm ioctl: add a device mapper ioctl function.

2018-09-25 Thread Helen Koike
From: Enric Balletbo i Serra Add a dm_ioctl_cmd to issue the equivalent of a DM ioctl call in kernel. Signed-off-by: Enric Balletbo i Serra --- drivers/md/dm-ioctl.c | 50 +++ include/linux/device-mapper.h | 6 + 2 files changed, 56 insertions(+)

[dm-devel] [PATCH 0/2] boot to a mapped device

2018-09-25 Thread Helen Koike
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

[dm-devel] [PATCH 2/2] init: add support to directly boot to a mapped device

2018-09-25 Thread Helen Koike
to use dm_ioctl calls] Signed-off-by: Enric Balletbo i Serra [rework to use concise format | rework for upstream] Signed-off-by: Helen Koike --- .../admin-guide/kernel-parameters.rst | 1 + .../admin-guide/kernel-parameters.txt | 3 + Documentation/device-mapper/dm-boot.txt