From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@infradead.org>,
dm-devel@redhat.com, Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.com>
Subject: Re: dm-mpath: always return reservation conflict
Date: Thu, 29 Sep 2016 17:35:03 +0200 [thread overview]
Message-ID: <20160929153502.GC32512@lst.de> (raw)
In-Reply-To: <20160929150132.GA31965@redhat.com>
On Thu, Sep 29, 2016 at 11:01:33AM -0400, Mike Snitzer wrote:
> I've elected to just take this change for 4.9. Please see:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.9&id=8ff232c1a819c2e98d85974a3bff0b7b8e2970ed
Thanks Mike.
If any problems show up I will send you an incremental patch that limits
this behavior to devices where we created reservations using the kernel
pr_ops API.
next prev parent reply other threads:[~2016-09-29 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:36 [PING / RESEND] handling reservation conflicts in dm-mpath Christoph Hellwig
2016-08-02 12:36 ` [PATCH] dm-mpath: always return reservation conflict Christoph Hellwig
2016-08-11 18:38 ` [dm-devel] " Christoph Hellwig
2016-08-15 13:08 ` Mike Snitzer
2016-08-15 13:40 ` Mike Snitzer
2016-09-26 16:52 ` [dm-devel] " Christoph Hellwig
2016-09-26 19:06 ` James Bottomley
2016-09-27 6:34 ` Hannes Reinecke
2016-09-27 18:50 ` James Bottomley
2016-09-29 15:01 ` Mike Snitzer
2016-09-29 15:35 ` Christoph Hellwig [this message]
2016-09-30 0:55 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2015-07-15 11:23 [PATCH] " Hannes Reinecke
2015-07-15 11:35 ` James Bottomley
2015-07-15 11:52 ` Hannes Reinecke
2015-07-15 12:01 ` James Bottomley
2015-07-15 12:15 ` Hannes Reinecke
2015-07-15 13:20 ` Mike Snitzer
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=20160929153502.GC32512@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@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.