| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: tip.git regression from "vsprintf: unify the format
What is the issue status in meantime ?
git pull reports conflicting merge ./lib/vsprintf.c
PV DomUs may be brought up , but cannot be
shutdown.
Boris.
--- On Sat, 3/14/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
To: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Frederic Weisbecker" <fweisbec@xxxxxxxxx>, "Ingo Molnar" <mingo@xxxxxxx>, "the arch/x86 maintainers" <x86@xxxxxxxxxx>, "Linux Kernel Mailing List" <linux-kernel@xxxxxxxxxxxxxxx>
Date: Saturday, March 14, 2009, 12:11 PM
Vegard Nossum wrote:
> 2009/3/14 Jeremy Fitzhardinge <jeremy@xxxxxxxx>:
>
>> Change fef20d9c1380f04ba9492d6463148db07b413708, "vsprintf: unify
the format
>> decoding layer for its 3 users", causes a regression in xenbus
which results
>> in no devices getting attached to a new domain. Reverting
>> fef20d9c1380f04ba9492d6463148db07b413708 and
>> 39e874f8afbdb3745e2406ce4ecbde9ac4cbaa78 fixes the problem.
>>
>> I haven't identified what format string is being handled wrongly,
so I don't
>> know what the precise bug is. The most complex looking format in use
seems
>> to be %.*s; there's also "%s/%s", "%i" and
"%lX".
>>
>
> Hi,
>
> At least %.*s seems to be broken. How about this patch?
>
Thanks, that does the trick.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home