Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1338769 > unrolled thread
| Started by | Kees Cook <keescook@chromium.org> |
|---|---|
| First post | 2016-02-20 19:20 +0100 |
| Last post | 2016-02-22 20:00 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH v5 0/3] init: add support to directly boot to a mapped device Kees Cook <keescook@chromium.org> - 2016-02-20 19:20 +0100
Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device Alasdair G Kergon <agk@redhat.com> - 2016-02-21 23:10 +0100
Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device Kees Cook <keescook@chromium.org> - 2016-02-22 20:00 +0100
| From | Kees Cook <keescook@chromium.org> |
|---|---|
| Date | 2016-02-20 19:20 +0100 |
| Subject | [PATCH v5 0/3] init: add support to directly boot to a mapped device |
| Message-ID | <r4kim-1jY-9@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Alasdair G Kergon <agk@redhat.com> |
|---|---|
| Date | 2016-02-21 23:10 +0100 |
| Subject | Re: [PATCH v5 0/3] init: add support to directly boot to a mapped device |
| Message-ID | <r4Kmt-4bO-11@gated-at.bofh.it> |
| In reply to | #1338769 |
On Sat, Feb 20, 2016 at 10:13:49AM -0800, Kees Cook wrote: > 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/ Inconsistencies in the terminology here can be sorted out during review, and I see that you've taken on board some of my review comments from 2010, but what are your responses to the rest of them? Alasdair
[toc] | [prev] | [next] | [standalone]
| From | Kees Cook <keescook@chromium.org> |
|---|---|
| Date | 2016-02-22 20:00 +0100 |
| Message-ID | <r53Sb-1FT-23@gated-at.bofh.it> |
| In reply to | #1339001 |
On Sun, Feb 21, 2016 at 2:08 PM, Alasdair G Kergon <agk@redhat.com> wrote: > On Sat, Feb 20, 2016 at 10:13:49AM -0800, Kees Cook wrote: >> 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/ > > Inconsistencies in the terminology here can be sorted out during review, > and I see that you've taken on board some of my review comments from > 2010, but what are your responses to the rest of them? Ah, sorry, the threads I could find were incomplete, so I wasn't able to find those comments that were made to Will's 2010 submission. In some of the cleanups I did I was very confused about "target" vs "table", and tried to fix that. Regardless, I'm open to fixing whatever is needed. :) Thanks for looking at this again! -Kees -- Kees Cook Chrome OS & Brillo Security
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web