[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DF23A92.8050909@redhat.com>
Date: Fri, 10 Jun 2011 17:38:58 +0200
From: Igor Mammedov <imammedo@...hat.com>
To: Tim Deegan <Tim.Deegan@...rix.com>
CC: Pasi K?rkk?inen <pasik@....fi>, xen-devel@...ts.xensource.com,
Keir Fraser <keir@....org>,
Stabellini <stefano.stabellini@...citrix.com>,
"containers@...ts.linux-foundation.org"
<containers@...ts.linux-foundation.org>,
Li Zefan <lizf@...fujitsu.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.cz>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Keir Fraser <keir.xen@...il.com>,
Paul Menage <menage@...gle.com>,
Hiroyuki Kamezawa <kamezawa.hiroyuki@...il.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>
Subject: Re: [Xen-devel] Possible shadow bug
On 06/10/2011 02:40 PM, Tim Deegan wrote:
> At 14:48 +0300 on 10 Jun (1307717301), Pasi K?rkk?inen wrote:
>> On Fri, Jun 10, 2011 at 11:10:11AM +0100, Tim Deegan wrote:
>>> At 11:01 +0100 on 10 Jun (1307703699), Tim Deegan wrote:
>>>> ISTR that even though the RHEL xen reports a 3.0.x version it has quite
>>>> a lot of backports in it. Does it have this patch?
>>>> http://hg.uk.xensource.com/xen-3.1-testing.hg/rev/e8fca4c42d05
>>> Oops, that URL doesn't work; I meant this:
>>> http://xenbits.xen.org/xen-3.1-testing.hg/rev/e8fca4c42d05
>>>
>> RHEL5 Xen (hypervisor) reports version as 3.1.2-xyz..
> Based on a quick scrobble through the CentOS 5.6 SRPMs it looks like a
> 3.1.0 hypervisor with a bunch of extra patches, but not this one. This
> is very likely the cause of the crash in mem_cgroup_create(), and
> probably the corruptions too. That would explain why they didn't happen
> on a 4.0.x SLES11 Xen, but not really why the original patch in this
> thread made it go away.
>
Maybe it changes timing so that imul is executed with correct memory
content?
Putting extra printk inside zone loop or flushing tlb before it also
make problem
go away. Or may be problem just becomes invisible and memory is corrupted at
another place.
PS:
Well, never mind. I do not know what I'm talking about.
> Cheers,
>
> Tim.
>
--
Thanks,
Igor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists