From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: Ian.Pratt@eu.citrix.com
Cc: xen-devel@lists.xensource.com
Subject: RE: XCP: update dom0 kernel?
Date: Thu, 27 May 2010 13:31:17 +0900 (JST) [thread overview]
Message-ID: <20100527043117.479F671910@kuma.localdomain> (raw)
In-Reply-To: Your message of "Thu, 22 Apr 2010 10:43:32 +0100" <4FA716B1526C7C4DB0375C6DADBC4EA35562034FE8@LONPMAILBOX01.citrite.net>
hi,
>> i want to use linux md driver in xcp's dom0.
>> however, unfortunately the kernel shipped with xcp build20719 seems to
>> have a known deadlock bug and unusable for my purpose.
>>
>> in git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git,
>> the bug was introduced by:
>> 449aad3e25358812c43afc60918c5ad3819488e7
>> and fixed by:
>> c8c00a6915a2e3d10416e8bdd3138429beb96210
>>
>> any chance for it to be fixed for xcp soon?
>
> Thanks for the pointer -- it can definitely be fixed in the next update.
i heard that the next release will use the same kernel and thus will
have the bug intact. it's a bit disappointing. is it true?
YAMAMOTO Takashi
>
> One of the things we want to discuss at the summit next week is the schedule with which we should be aiming to release new XCP install ISOs.
>
> Thanks,
> Ian
>
>
>>
>> YAMAMOTO Takashi
next prev parent reply other threads:[~2010-05-27 4:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 4:48 XCP: update dom0 kernel? YAMAMOTO Takashi
2010-04-22 9:43 ` Ian Pratt
2010-05-11 7:14 ` YAMAMOTO Takashi
2010-05-11 8:45 ` Dave Scott
2010-05-11 10:16 ` Pasi Kärkkäinen
2010-05-12 6:22 ` xcp 0.2 (RE: XCP: update dom0 kernel?) YAMAMOTO Takashi
2010-05-12 18:15 ` Ian Pratt
2010-05-27 4:31 ` YAMAMOTO Takashi [this message]
2010-05-27 8:09 ` XCP: update dom0 kernel? Ian Pratt
2010-05-27 9:00 ` YAMAMOTO Takashi
2010-05-27 9:22 ` Ian Campbell
2010-06-25 8:42 ` YAMAMOTO Takashi
2010-06-25 8:47 ` Ian Campbell
2010-06-25 8:53 ` YAMAMOTO Takashi
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=20100527043117.479F671910@kuma.localdomain \
--to=yamamoto@valinux.co.jp \
--cc=Ian.Pratt@eu.citrix.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).