linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	LKML <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@suse.de>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: dm: improve block integrity support
Date: Thu, 14 Apr 2011 10:42:09 -0400	[thread overview]
Message-ID: <20110414144208.GA26155@redhat.com> (raw)
In-Reply-To: <20110414140925.GA25803@redhat.com>

On Thu, Apr 14 2011 at 10:09am -0400,
Mike Snitzer <snitzer@redhat.com> wrote:

> [trimming CCs so as not to pester as many people directly]
> 
> On Fri, Apr 01 2011 at  1:42pm -0400,
> Mike Snitzer <snitzer@redhat.com> wrote:
> 
> > The current block integrity (DIF/DIX) support in DM is verifying that
> > all devices' integrity profiles match during DM device resume (which
> > is past the point of no return).  To some degree that is unavoidable
> > (stacked DM devices force this late checking).  But for most DM
> > devices (which aren't stacking on other DM devices) the ideal time to
> > verify all integrity profiles match is during table load.
> > 
> > Introduce the notion of an "initialized" integrity profile: a profile
> > that was blk_integrity_register()'d with a non-NULL 'blk_integrity'
> > template.  Add blk_integrity_is_initialized() to allow checking if a
> > profile was initialized.
> > 
> > Update DM integrity support to:
> > - check all devices with _initialized_ integrity profiles match
> >   during table load; uninitialized profiles (e.g. for underlying DM
> >   device(s) of a stacked DM device) are ignored.
> > - disallow a table load that would result in an integrity profile that
> >   conflicts with a DM device's existing (in-use) integrity profile
> > - avoid clearing an existing integrity profile
> > - validate all integrity profiles match during resume; but if they
> >   don't all we can do is report the mismatch (during resume we're past
> >   the point of no return)
> > 
> > Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> > Cc: Martin K. Petersen <martin.petersen@oracle.com>
> 
> Hi Martin,
> 
> Any chance you've had a look at this?  I'm most interested in whether
> the code works with the various integrity profiles you have.
> 
> I'd really like to get this reviewed and queued for upstream so that it
> doesn't die on the vine.

Ah wow, just noticed this got in through the block tree over a week ago:
http://git.kernel.org/linus/a63a5cf84dac7a23a57

Thanks Jens!

Martin,
I've done enough testing that I am confident the DM integrity support is
in a better place with this change.  But I'd still really appreciate it
if you could verify all is well.

Mike

  reply	other threads:[~2011-04-14 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 22:35 [Regression] Please revert a91a2785b20 Thomas Gleixner
2011-03-28 22:43 ` Thomas Gleixner
2011-03-28 23:03   ` Mike Snitzer
2011-03-29  6:59     ` Jens Axboe
2011-03-29 13:20       ` Mike Snitzer
2011-03-29 13:35         ` James Bottomley
2011-03-29 13:42         ` Martin K. Petersen
2011-03-29 13:58           ` Need to refactor DM's integrity profile support a bit (was: Re: Please revert a91a2785b20) Mike Snitzer
2011-04-01 17:42             ` [PATCH] dm: improve block integrity support Mike Snitzer
2011-04-14 14:09               ` Mike Snitzer
2011-04-14 14:42                 ` Mike Snitzer [this message]
2011-04-15  4:57                   ` Martin K. Petersen
2011-04-05  2:09           ` Please revert a91a2785b20 NeilBrown
2011-03-28 22:45 ` [Regression] " Martin K. Petersen
2011-03-28 23:03   ` Thomas Gleixner
2011-03-29  0:09     ` Martin K. Petersen
2011-03-29  0:11       ` Martin K. Petersen
2011-03-29  2:32       ` Thomas Gleixner
2011-03-29  5:32       ` Giacomo Catenazzi

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=20110414144208.GA26155@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).