From: Juergen Kreileder <jk@blackdown.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Alasdair G Kergon <agk@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: BUG at drivers/md/kcopyd.c:146
Date: Fri, 21 Apr 2006 17:12:47 +0200 [thread overview]
Message-ID: <871wvraro0.fsf@blackdown.de> (raw)
In-Reply-To: <20060420124852.17dc7417.akpm@osdl.org> (Andrew Morton's message of "Thu, 20 Apr 2006 12:48:52 -0700")
Andrew Morton <akpm@osdl.org> writes:
> (restored Juergen's cc)
[The cc list was correct actually, I had set a Mail-Followup-To header.]
> Alasdair G Kergon <agk@redhat.com> wrote:
>>
>> On Sat, Apr 15, 2006 at 01:19:51PM +0200, Juergen Kreileder wrote:
[...]
>> I found several bugs in the snapshot code when I reviewed it,
>> including (thankfully hard-to-trigger) silent data corruption.
>>
>> Patches went into 2.6.17-rc1. [There's one unfinished patch
>> outstanding for a theoretical race that I've only been able to
>> reproduce under artificial conditions.]
>>
>>> kernel BUG at drivers/md/kcopyd.c:146!
>>
>> Probably needs this patch (12th March):
>>
>> dm snapshot: fix kcopyd destructor
>>
>
> Thanks, I've appended a copy here.
>
> Juergen, can you please test this?
Works fine so far but it's too early to call it fixed.
I'll let it run over the weekend and report back.
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://blog.blackdown.de/
next prev parent reply other threads:[~2006-04-21 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 21:11 [PATCH 1/9] device-mapper snapshot: load metadata on creation Alasdair G Kergon
2006-01-23 5:33 ` Andrew Morton
2006-01-23 15:34 ` Alasdair G Kergon
2006-04-15 11:19 ` BUG at drivers/md/kcopyd.c:146 (was: [PATCH 1/9] device-mapper snapshot: load metadata on creation) Juergen Kreileder
2006-04-20 17:05 ` Alasdair G Kergon
2006-04-20 19:48 ` Andrew Morton
2006-04-21 15:12 ` Juergen Kreileder [this message]
2006-04-24 18:31 ` BUG at drivers/md/kcopyd.c:146 Juergen Kreileder
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=871wvraro0.fsf@blackdown.de \
--to=jk@blackdown.de \
--cc=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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