On Tue, Oct 27, 2020 at 05:17:31PM -0700, Eric Biggers wrote:
> On Tue, Oct 27, 2020 at 11:58:47PM +, Satya Tangirala wrote:
> > > > +/**
> > > > + * blk_ksm_update_capabilities() - Update the restrictions of a KSM to
> > > > those of
> > > > + *another KSM
> >
On Tue, Oct 27, 2020 at 11:58:47PM +, Satya Tangirala wrote:
> > > +/**
> > > + * blk_ksm_update_capabilities() - Update the restrictions of a KSM to
> > > those of
> > > + * another KSM
> > > + * @target_ksm: The KSM whose restrictions to update.
> > > + *
On Tue, Oct 27, 2020 at 02:31:51PM -0700, Eric Biggers wrote:
> On Thu, Oct 15, 2020 at 09:46:31PM +, Satya Tangirala wrote:
> > Update the device-mapper core to support exposing the inline crypto
> > support of the underlying device(s) through the device-mapper device.
> >
> > This works by
On Thu, Oct 15, 2020 at 09:46:31PM +, Satya Tangirala wrote:
> Update the device-mapper core to support exposing the inline crypto
> support of the underlying device(s) through the device-mapper device.
>
> This works by creating a "passthrough keyslot manager" for the dm
> device, which
Hi Satya,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on dm/for-next]
[also build test WARNING on block/for-next linus/master linux/master v5.9
next-20201023]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch,
Update the device-mapper core to support exposing the inline crypto
support of the underlying device(s) through the device-mapper device.
This works by creating a "passthrough keyslot manager" for the dm
device, which declares support for encryption settings which all
underlying devices support.
6 matches
Mail list logo
