From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, dm-devel@redhat.com
Subject: Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
Date: Sat, 25 Apr 2015 08:37:32 -0700 [thread overview]
Message-ID: <20150425153732.GA10612@infradead.org> (raw)
In-Reply-To: <20150425152856.GB28453@redhat.com>
On Sat, Apr 25, 2015 at 11:28:57AM -0400, Mike Snitzer wrote:
> On Sat, Apr 25 2015 at 5:23am -0400,
> Christoph Hellwig <hch@infradead.org> wrote:
>
> > Running dm-mpath against a tcm_loop target with two ALUA paths makes
> > the kernel very unhappy when CONFIG_DM_MQ_DEFAULT is set. Without it
> > it's perfectly happy.
>
> Wonder if commit 63a4f065ec ("dm: fix add_disk() NULL pointer due to
> race with free_dev()") left something not quite right relative to
> blk-mq? Or maybe this is a problem confined to blk-mq itself.
I'll give it a spin.
> What were you actually testing when this happened? Were you failing
> paths under IO load or something?
This happened on the initial udev-direct scan of the devices.
> Also, which upstream commit was your tree based on? Did you have any
> non-upstream patches applied that I should be aware of?
Latest Linus tree as of this morning.
next prev parent reply other threads:[~2015-04-25 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 9:23 CONFIG_DM_MQ_DEFAULT makes my kernel unhappy Christoph Hellwig
2015-04-25 15:28 ` Mike Snitzer
2015-04-25 15:37 ` Christoph Hellwig [this message]
2015-04-26 14:16 ` Christoph Hellwig
2015-04-27 15:59 ` Mike Snitzer
2015-04-27 16:03 ` Christoph Hellwig
2015-04-27 19:03 ` Mike Snitzer
2015-04-29 0:59 ` [PATCH] dm: fix blk-mq request-based DM queue initialization Mike Snitzer
2015-04-29 13:00 ` Christoph Hellwig
2015-04-30 1:41 ` Mike Snitzer
2015-04-30 7:22 ` Christoph Hellwig
2015-04-30 8:23 ` Christoph Hellwig
2015-04-30 12:47 ` 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=20150425153732.GA10612@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox