[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] xen/arm: Crash when allocating memory for ACPI table (Was Re: Design doc of adding ACPI support for arm64 on Xen - version 2)
- To: Shannon Zhao <shannon.zhao@xxxxxxxxxx>, Shannon Zhao <zhaoshenglong@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>, "Ian Campbell" <ian.campbell@xxxxxxxxxx>, Parth Dixit <parth.dixit@xxxxxxxxxx>, Christoffer Dall <christoffer.dall@xxxxxxxxxx>
- From: Julien Grall <julien.grall@xxxxxxxxxx>
- Date: Fri, 14 Aug 2015 15:53:17 +0100
- Cc: Hangaohuai <hangaohuai@xxxxxxxxxx>, "Huangpeng \(Peter\)" <peter.huangpeng@xxxxxxxxxx>
- Delivery-date: Fri, 14 Aug 2015 14:54:29 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 14/08/15 15:49, Shannon Zhao wrote:
>> Ok, so it's likely a memory corruption. You need to check the bound you
>> ara using when copying the data to the guest or from the ACPI in
>> general. Or maybe you just didn't allocate enough space.
>>
>
> But it fails at the xzalloc_bytes itself. not at copy function.
Because the previous copy may have overwritten the metadata of the
memory allocator...
If those metadata are corrupted, xalloc_bytes we act weirdly such as
crashing Xen.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
