On Mon, 2019-10-07 at 10:05 +0200, Markus Armbruster wrote: > Maxim Levitsky <mlevi...@redhat.com> writes: > > > On Fri, 2019-09-20 at 17:14 -0400, John Snow wrote: > > > > > > On 9/12/19 6:30 PM, Maxim Levitsky wrote: > > > > This patch series is continuation of my work to add encryption > > > > key managment to luks/qcow2 with luks. > > > > > > > > This is second version of this patch set. > > > > The changes are mostly addressing the review feedback, > > > > plus I tested (and fixed sadly) the somewhat ugly code > > > > that allows to still write share a raw luks device, > > > > while preveting the key managment from happening in this case, > > > > as it is unsafe. > > > > I added a new iotest dedicated to that as well. > > > > > > > > Best regards, > > > > Maxim Levitsky > > > > > > > > > > What branch is this based on? > > > It doesn't seem to apply to origin/master. > > > > > > --js > > > > It is based on refactoring patch series I send before, > > which is also under review: > > "[PATCH v2 00/13] RFC crypto/luks: preparation for encryption key managment" > > Recommend to note such dependencies in the cover letter as > > Based-on: <message-id> I'll take a note! Note that now all these patches are merged thus, this patch series should more or less apply on top of master branch. I'll probably resend a V3 after I finish going over the review of this series.
Best regards, Maxim Levitsky