From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: bug in hvmloader xenbus_shutdown logic Date: Wed, 4 Dec 2013 09:49:44 +0000 Message-ID: <1386150584.15530.7.camel@kazak.uk.xensource.com> References: <0E6BCB61859D7F4EB9CAC75FC6EE6FF844B9280C@SZXEMA502-MBX.china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0E6BCB61859D7F4EB9CAC75FC6EE6FF844B9280C@SZXEMA502-MBX.china.huawei.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Liuqiming (John)" Cc: Yanqiangjun , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Wed, 2013-12-04 at 04:25 +0000, Liuqiming (John) wrote: > memset can not set all the page to zero in an atomic way, and during > the clear up process oxenstored may access this ring. Why is oxenstored poking at the ring? Surely it should only do so when the guest (hvmloader) sends it a request. If hvmloader is clearing the page while there is a request/event outstanding then this is an hvmloader bug. Ian.