Linux Device Mapper development
 help / color / mirror / Atom feed
From: Nikolay Borisov <n.borisov@siteground.com>
To: thornber@redhat.com
Cc: device-mapper development <dm-devel@redhat.com>,
	SiteGround Operations <operations@siteground.com>
Subject: Re: Fwd: kernel BUG at drivers/md/persistent-data/dm-btree-remove.c:182!
Date: Mon, 19 Oct 2015 13:45:31 +0300	[thread overview]
Message-ID: <5624C9CB.7000702@siteground.com> (raw)
In-Reply-To: <20151019103057.GA14688@rh-vpn>



On 10/19/2015 01:30 PM, Joe Thornber wrote:
> On Mon, Oct 19, 2015 at 12:16:53PM +0300, Nikolay Borisov wrote:
>> [Resending as I had typo in the dm-devel's mailing list the first time]
>>
>> Hello, 
>>
>> Using kernel 3.12.47 I've hit the aforementioned issue. I'd also like 
>> to say that this kernel does include Dennis Yang's patch which 
>> supposedly fixes a similar issue 
>> (https://www.redhat.com/archives/dm-devel/2015-May/msg00113.html). 
> 
> 
> Did you apply this patch or my corrected patch?
> 
> https://www.redhat.com/archives/dm-devel/2015-May/msg00123.html

I haven't applied anything per-se, rather this stable kernel does
include your corrected patch. So yes, the correct fix for the issue
reported by Dennis is included, yet apparently the same issue is
manifesting again.


> 
> - Joe
> 

  reply	other threads:[~2015-10-19 10:45 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 [this message]
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
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=5624C9CB.7000702@siteground.com \
    --to=n.borisov@siteground.com \
    --cc=dm-devel@redhat.com \
    --cc=operations@siteground.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