All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-scsi@vger.kernel.org
Subject: Re: dm: Integrity errors should not cause failover
Date: Tue, 8 Mar 2011 10:30:52 -0500	[thread overview]
Message-ID: <20110308153052.GC4669@redhat.com> (raw)
In-Reply-To: <1299597625.2476.23.camel@mulgrave.site>

On Tue, Mar 08 2011 at 10:20am -0500,
James Bottomley <James.Bottomley@suse.de> wrote:

> On Tue, 2011-03-08 at 10:14 -0500, Mike Snitzer wrote:
> > On Tue, Mar 08 2011 at  1:54am -0500,
> > Martin K. Petersen <martin.petersen@oracle.com> wrote:
> > 
> > > 
> > > Integrity errors need to be passed to the owner of the integrity
> > > metadata for processing. Consequently EILSEQ should be passed up the
> > > stack.
> > > 
> > > Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
> > 
> > Acked-by: Mike Snitzer <snitzer@redhat.com>
> > 
> > Thanks Martin.  But James has already staged a few patches associated
> > with IO error differentation for 2.6.39.  Your dm-mpath patch will need
> > to be rebased on that work; best to feed it to James too.
> > 
> > (we were gambling that there wouldn't be additional DM or block changes
> > related to this work and figured it safe to have James carry all the
> > SCSI, block and DM changes... ;)
> > 
> > Problem is I'm not seeing a 2.6.39 branch in James' scsi-2.6-misc.git
> > (even though I know the changes are staged there ;)
> > 
> > See:
> > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=79775567e0439ca47eb9f501e52c4b713d44cf89
> > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=751b2a7d623ead9e55f751a6087efeab454b5659
> > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=63583cca745f440167bf27877182dc13e19d4bcf
> > 
> > James,
> > Any easy way to get Martin your 2.6.39 tree?  Do you have a branch (just
> > the tag isn't exposed)?
> 
> Branch for what?  It's a linear tree with all the SCSI patches on
> master.

Ah.. good to know.  I hadn't looked that closely ;)

But now that I look, you've been quite busy!  The above commits are
buried pretty deep by now.

Mike

  reply	other threads:[~2011-03-08 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  6:54 [PATCH] dm: Integrity errors should not cause failover Martin K. Petersen
2011-03-08 15:14 ` Mike Snitzer
2011-03-08 15:20   ` James Bottomley
2011-03-08 15:30     ` Mike Snitzer [this message]
2011-03-08 15:24   ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2011-05-18  4:49 [PATCH] " Martin K. Petersen
2011-05-18 12:11 ` Mike Snitzer
2011-05-23 18:17   ` Mike Snitzer
2011-05-25 15:04     ` Martin K. Petersen

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=20110308153052.GC4669@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@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 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.