From: Nikolay Borisov <n.borisov@siteground.com>
To: Dennis Yang <shinrairis@gmail.com>,
device-mapper development <dm-devel@redhat.com>,
SiteGround Operations <operations@siteground.com>,
thornber@redhat.com
Subject: Re: kernel BUG at drivers/md/persistent-data/dm-btree-remove.c:182!
Date: Thu, 22 Oct 2015 10:59:32 +0300 [thread overview]
Message-ID: <56289764.4010009@siteground.com> (raw)
In-Reply-To: <20151021174939.GA3144@rh-vpn>
On 10/21/2015 08:49 PM, Joe Thornber wrote:
> On Tue, Oct 20, 2015 at 10:39:31AM +0800, Dennis Yang wrote:
>> Hi,
>>
>> After I analyzed the metadata of this case couple months ago, I find
>> out that there is another possible bug which might trigger this
>> assertion fail in shift(). I had posted a patch two months ago on the
>> list to explain and fix this issue. Could you help reviewing this?
>>
>> https://www.redhat.com/archives/dm-devel/2015-August/msg00155.html
>
> Yep, that's a bug. Sorry I missed it before when you posted. Here's
> my fix:
Thanks for that, I will apply this and report back if I experience the
same issue. But looking at your test case I'm confident this should fix
the issue. Dennis' patch in contrast still causes the within_one assert
to fail.
Are you going to tag this for stable ?
next prev parent reply other threads:[~2015-10-22 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5624B4B8.1030404@siteground.com>
2015-10-19 9:16 ` Fwd: kernel BUG at drivers/md/persistent-data/dm-btree-remove.c:182! Nikolay Borisov
2015-10-19 10:30 ` Joe Thornber
2015-10-19 10:45 ` Nikolay Borisov
2015-10-19 16:02 ` Mike Snitzer
2015-10-20 2:39 ` Dennis Yang
2015-10-20 7:35 ` Nikolay Borisov
2015-10-20 14:35 ` Joe Thornber
2015-10-21 17:49 ` Joe Thornber
2015-10-22 7:59 ` Nikolay Borisov [this message]
2015-10-20 12:57 ` Nikolay Borisov
2015-10-20 14:35 ` Joe Thornber
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=56289764.4010009@siteground.com \
--to=n.borisov@siteground.com \
--cc=dm-devel@redhat.com \
--cc=operations@siteground.com \
--cc=shinrairis@gmail.com \
--cc=thornber@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