From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, Heinz Diehl <htd@fancy-poultry.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [dm-devel] Re: todays git regression (2.6.32-04008.g3ff6a46): lot of device mapper warnings
Date: Fri, 11 Dec 2009 11:47:40 -0500 [thread overview]
Message-ID: <yq13a3hv4nn.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <200912111028.05512.borntraeger@de.ibm.com> (Christian Borntraeger's message of "Fri, 11 Dec 2009 10:28:05 +0100")
>>>>> "Christian" == Christian Borntraeger <borntraeger@de.ibm.com> writes:
Christian> any news on the final fix? Do you want Heinz and me to verify
Christian> your fix on our systems?
Looking into this issue unearthed an unrelated problem with the topology
stacking algorithm that turns out to be much trickier to fix. That's
what's taking time.
Since the first bug is simply causing a warning I'm inclined to get
everything fixed up before having Jens queue a fix. Shouldn't be more
than a day or two before I have all this worked out.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-12-11 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 9:49 todays git regression (2.6.32-04008.g3ff6a46): lot of device mapper warnings Christian Borntraeger
2009-12-09 21:25 ` Heinz Diehl
2009-12-09 21:45 ` Jens Axboe
2009-12-09 22:07 ` Jens Axboe
2009-12-10 0:56 ` Mike Snitzer
2009-12-10 1:14 ` Martin K. Petersen
2009-12-11 9:28 ` Christian Borntraeger
2009-12-11 16:47 ` Martin K. Petersen [this message]
2009-12-10 11:08 ` Christian Borntraeger
2009-12-10 14:08 ` Heinz Diehl
2009-12-12 1:51 ` Christian Kujau
2009-12-15 21:58 ` Christian Kujau
2009-12-15 22:02 ` Jens Axboe
2009-12-15 22:08 ` Martin K. Petersen
2009-12-15 22:16 ` Jens Axboe
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=yq13a3hv4nn.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=dm-devel@redhat.com \
--cc=htd@fancy-poultry.org \
--cc=jens.axboe@oracle.com \
--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