Hi Mimi,
On 7/21/21 2:17 PM, Mimi Zohar wrote:
On Wed, 2021-07-21 at 12:07 -0400, Mimi Zohar wrote:
On Wed, 2021-07-21 at 11:42 -0400, Mike Snitzer wrote:
On Tue, Jul 20 2021 at 10:12P -0400,
Mimi Zohar wrote:
Hi Tushar, Mike,
On Mon, 2021-07-12 at 17:48 -0700, Tushar Sugandhi wrote:
+str
On Wed, 2021-07-21 at 12:07 -0400, Mimi Zohar wrote:
> On Wed, 2021-07-21 at 11:42 -0400, Mike Snitzer wrote:
> > On Tue, Jul 20 2021 at 10:12P -0400,
> > Mimi Zohar wrote:
> >
> > > Hi Tushar, Mike,
> > >
> > > On Mon, 2021-07-12 at 17:48 -0700, Tushar Sugandhi wrote:
> > > > +struct dm_ima_de
On Wed, 2021-07-21 at 11:42 -0400, Mike Snitzer wrote:
> On Tue, Jul 20 2021 at 10:12P -0400,
> Mimi Zohar wrote:
>
> > Hi Tushar, Mike,
> >
> > On Mon, 2021-07-12 at 17:48 -0700, Tushar Sugandhi wrote:
> > > +struct dm_ima_device_table_metadata {
> > > + /*
> > > +* Contains data
On Tue, Jul 20 2021 at 10:12P -0400,
Mimi Zohar wrote:
> Hi Tushar, Mike,
>
> On Mon, 2021-07-12 at 17:48 -0700, Tushar Sugandhi wrote:
> > +struct dm_ima_device_table_metadata {
> > + /*
> > +* Contains data specific to the device which is common across
> > +* all the tar
Hi Tushar, Mike,
On Mon, 2021-07-12 at 17:48 -0700, Tushar Sugandhi wrote:
> +struct dm_ima_device_table_metadata {
> + /*
> +* Contains data specific to the device which is common across
> +* all the targets in the table.e.g. name, uuid, major, minor etc.
> +* The v
DM configures a block device with various target specific attributes
passed to it as a table. DM loads the table, and calls each target’s
respective constructors with the attributes as input parameters.
Some of these attributes are critical to ensure the device meets
certain security bar. Thus, I
