From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: device-mapper development <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
Date: Mon, 26 May 2014 14:29:32 +0200 [thread overview]
Message-ID: <538333AC.60103@suse.de> (raw)
In-Reply-To: <53833183.7080106@acm.org>
On 05/26/2014 02:20 PM, Bart Van Assche wrote:
> On 05/26/14 14:10, Hannes Reinecke wrote:
>> Mike Snitzer had a patch in his device-mapper tree:
>>
>> dm mpath: fix lock order inconsistency in multipath_ioctl (2014-05-14
>> 16:12:17 -0400)
>>
>> I was sort of hoping that would address this issue.
>> Can you check?
>
> Hello Hannes,
>
> Is it possible that that patch already got included in v3.15-rc6 and
> hence that that patch was included in my test ?
>
> $ git log v3.15-rc5..v3.15-rc6 | grep 'dm mpath: fix lock order
> inconsistency in multipath_ioctl'
> dm mpath: fix lock order inconsistency in multipath_ioctl
> dm mpath: fix lock order inconsistency in multipath_ioctl
>
Could be.
Okay, I'll be cross-checking.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2014-05-26 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 9:31 3.15-rc4: circular locking dependency triggered by dm-multipath Bart Van Assche
2014-05-06 13:22 ` Mike Snitzer
2014-05-06 13:46 ` Bart Van Assche
2014-05-07 20:53 ` Mike Snitzer
2014-05-08 5:57 ` Hannes Reinecke
2014-05-26 11:44 ` Bart Van Assche
2014-05-26 12:10 ` Hannes Reinecke
2014-05-26 12:20 ` Bart Van Assche
2014-05-26 12:29 ` Hannes Reinecke [this message]
2014-05-26 12:44 ` Hannes Reinecke
2014-05-26 12:51 ` Hannes Reinecke
2014-05-26 14:54 ` Bart Van Assche
2014-05-27 13:22 ` Mike Snitzer
2014-05-27 14:49 ` Mike Snitzer
2014-05-27 16:09 ` Bart Van Assche
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=538333AC.60103@suse.de \
--to=hare@suse.de \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--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.