From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm mpath: Fix a dm_blk_ioctl() deadlock
Date: Tue, 28 Jun 2016 14:59:14 -0400 [thread overview]
Message-ID: <20160628185913.GA8185@redhat.com> (raw)
In-Reply-To: <f2f4fe18-b3e0-30f6-5f4f-0fee385bade8@sandisk.com>
On Tue, Jun 28 2016 at 2:29pm -0400,
Bart Van Assche <bart.vanassche@sandisk.com> wrote:
> On 06/28/2016 08:15 PM, Mike Snitzer wrote:
> > This patch doesn't make sense.
> >
> > In the context of dm-mpath.c:multipath_prepare_ioctl, *bdev is only
> > valid if r == 0. But r == -ENOTCONN so how can *bdev be valid?
>
> Sorry but the dm code is not my area of expertise. How about the patch
> below? Please note that so far only the queue-length path selector has
> been tested.
Can we go back to what it is you've experienced? is it that you have
'queue_if_no_path' enabled and are issuing ioctls to an mpath device
(while removing underlying paths) you'll experience a live-lock (_not_
deadlock) once no valid paths exist?
If that isn't what you're hitting then I'd like to better understand how
a request_queue that is "dying" isn't able to keep itself up enough to
fail IO issued to it (to allow normal error handling to trap the IO
failure).
Mike
next prev parent reply other threads:[~2016-06-28 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:07 [PATCH] dm mpath: Fix a dm_blk_ioctl() deadlock Bart Van Assche
2016-06-28 18:15 ` Mike Snitzer
2016-06-28 18:29 ` Bart Van Assche
2016-06-28 18:59 ` Mike Snitzer [this message]
2016-06-28 19:16 ` Bart Van Assche
2016-06-28 19:33 ` 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=20160628185913.GA8185@redhat.com \
--to=snitzer@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@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 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).