From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: xen/arm: Crash when allocating memory for ACPI table (Was Re: Design doc of adding ACPI support for arm64 on Xen - version 2) Date: Fri, 14 Aug 2015 15:53:17 +0100 Message-ID: <55CE00DD.8020303@citrix.com> References: <55C413D5.7000709@huawei.com> <55CAF41C.1090208@huawei.com> <55CB0DC0.4020304@citrix.com> <55CDF5A3.8050201@linaro.org> <55CDF87C.40103@citrix.com> <55CDFCBD.608@linaro.org> <55CDFE20.3070208@citrix.com> <55CDFFFB.5070707@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55CDFFFB.5070707@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Shannon Zhao , Shannon Zhao , xen-devel , Jan Beulich , Stefano Stabellini , Ian Campbell , Parth Dixit , Christoffer Dall Cc: Hangaohuai , "Huangpeng (Peter)" List-Id: xen-devel@lists.xenproject.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