From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: dmcache RAID1 bug?
Date: Thu, 20 Nov 2014 14:10:04 +0000 [thread overview]
Message-ID: <20141120141003.GB16741@debian> (raw)
In-Reply-To: <20141120140426.GA16741@debian>
On Thu, Nov 20, 2014 at 02:04:26PM +0000, Joe Thornber wrote:
> On Wed, Nov 19, 2014 at 07:39:44PM -0200, Leonardo Santos wrote:
> > After run regression tests using 'git bisect', I identify that the error
> > was created after commit 8c081b52c6833a30a69ea3bdcef316eccc740c87
> >
> > To reproduce this error just:
> > - create a raid1 HDDs for origin device;
> > - create a cache device with SSDs (could or not be raid)
> > - create a metadata device with SSDs (could or not be raid)
> > - create a cache device using prior devices
> > - kernel crashes.
> >
> > @@ -1115,8 +1142,7 @@ static void check_for_quiesced_migrations(struct cache *cache,
> > return;
> >
> > INIT_LIST_HEAD(&work);
> > - if (pb->all_io_entry)
> > - dm_deferred_entry_dec(pb->all_io_entry, &work);
> > + dm_deferred_entry_dec(pb->all_io_entry, &work);
> >
> > if (!list_empty(&work))
> > queue_quiesced_migrations(cache, &work);
>
> This looks suspicious, I believe the all_io_entry is not set if the io
> covers a complete block. Any chance you could test with this fragment
> backed out please?
Ignore me, there's another check for !pb->all_io_entry.
next prev parent reply other threads:[~2014-11-20 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:24 dmcache RAID1 bug? Leonardo Santos
2014-11-17 14:46 ` Mike Snitzer
2014-11-17 18:14 ` Leonardo Santos
2014-11-18 18:18 ` Leonardo Santos
2014-11-19 21:39 ` Leonardo Santos
2014-11-20 4:19 ` Mike Snitzer
2014-11-20 14:04 ` Joe Thornber
2014-11-20 14:10 ` Joe Thornber [this message]
2015-02-06 16: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=20141120141003.GB16741@debian \
--to=thornber@redhat.com \
--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