All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: dmitry.kasatkin@intel.com
Cc: device-mapper development <dm-devel@redhat.com>,
	mpatocka@redhat.com, Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: dm-bufio
Date: Fri, 23 Mar 2012 17:32:21 -0400	[thread overview]
Message-ID: <20120323213110.GA11054@redhat.com> (raw)
In-Reply-To: <CALLzPKZcArim2WxockC6mKfcDNBJxhqt6_yvNqmFV0tPm6Z40A@mail.gmail.com>

On Fri, Mar 23 2012 at 11:17am -0400,
Kasatkin, Dmitry <dmitry.kasatkin@intel.com> wrote:

> On Fri, Mar 23, 2012 at 4:32 PM, Mike Snitzer <snitzer@redhat.com> wrote:
> > As an aside, just curious: what does your target do?
> 
> I have experimented with integrity protection.

Interesting.  Are you aware that a new integrity target has been
developed and is approaching upstream inclussion?  It is called
dm-verity.

Mikulas posted the most recent version here:
http://www.redhat.com/archives/dm-devel/2012-March/msg00133.html

And here is the userspace setup code:
http://www.redhat.com/archives/dm-devel/2012-March/msg00134.html

The original docs from Google's initial dm-verity are mostly applicable
(but need to be refreshed and included with the new version):
http://www.redhat.com/archives/dm-devel/2012-February/msg00119.html

dm-verity already has 2 formats, a 3rd could be added if you found the
existing formats somehow lacking, see:
http://www.redhat.com/archives/dm-devel/2012-March/msg00143.html

Mike

  reply	other threads:[~2012-03-23 21:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 11:01 dm-bufio Kasatkin, Dmitry
2012-03-23 11:10 ` dm-bufio Zdenek Kabelac
2012-03-23 11:26   ` dm-bufio Kasatkin, Dmitry
2012-03-23 14:12     ` dm-bufio Kasatkin, Dmitry
2012-03-23 14:21       ` dm-bufio Mike Snitzer
2012-03-23 14:29         ` dm-bufio Kasatkin, Dmitry
2012-03-23 14:32           ` dm-bufio Mike Snitzer
2012-03-23 15:17             ` dm-bufio Kasatkin, Dmitry
2012-03-23 21:32               ` Mike Snitzer [this message]
2012-03-24  0:04                 ` dm-bufio Kasatkin, Dmitry
2012-03-23 16:22       ` dm-bufio Mikulas Patocka
2012-03-23 23:58         ` dm-bufio Kasatkin, Dmitry
2012-03-24  1:07           ` dm-bufio Mikulas Patocka
2012-03-24 18:51             ` dm-bufio Will Drewry
2012-03-27 10:20               ` dm-bufio Kasatkin, Dmitry
2012-03-27  9:56             ` dm-bufio Kasatkin, Dmitry
  -- strict thread matches above, loose matches on Subject: below --
2011-10-14 19:14 [PATCH] dm-bufio Mikulas Patocka
2011-10-17 10:08 ` Joe Thornber
2011-10-17 12:41   ` dm-bufio Mike Snitzer
2011-10-13 15:05 dm-bufio Mikulas Patocka
2011-10-13 19:40 ` dm-bufio Mike Snitzer
2011-10-13 22:19   ` dm-bufio Mikulas Patocka
2011-10-13 22:31     ` dm-bufio Mike Snitzer
2011-10-14  9:19       ` dm-bufio Joe Thornber
2011-10-14  9:15 ` dm-bufio Joe Thornber
2011-10-14 12:19   ` dm-bufio Joe Thornber
2011-10-17 16:49   ` dm-bufio Mikulas Patocka
2011-10-17 18:01     ` dm-bufio Joe Thornber
2011-09-27 17:20 dm-bufio Mikulas Patocka
2011-09-28  9:41 ` dm-bufio Joe Thornber
2011-09-28  9:51 ` dm-bufio Heinz Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120323213110.GA11054@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=dmitry.kasatkin@intel.com \
    --cc=mpatocka@redhat.com \
    --cc=zkabelac@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.