From: Igor Mammedov <imammedo@redhat.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Stefano@phlegethon.org, Paul Menage <menage@google.com>,
xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>,
Stabellini <stefano.stabellini@eu.citrix.com>,
"containers@lists.linux-foundation.org"
<containers@lists.linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Keir Fraser <keir.xen@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
KAMEZAWA@phlegethon.org,
Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hiroyuki Kamezawa <kamezawa.hiroyuki@gmail.com>
Subject: Re: [Xen-devel] Possible shadow bug
Date: Fri, 10 Jun 2011 15:55:17 +0200 [thread overview]
Message-ID: <4DF22245.20008@redhat.com> (raw)
In-Reply-To: <20110610101011.GH5098@whitby.uk.xensource.com>
On 06/10/2011 12:10 PM, Tim Deegan wrote:
> At 11:01 +0100 on 10 Jun (1307703699), Tim Deegan wrote:
>> Actually, looking at the disassembly you posted, it looks more like it
>> might be an emulator bug in Xen; if Xen finds itself emulating the IMUL
>> instruction and either gets the logic wrong or does the memory access
>> wrong, it could cause that failure. And one reason that Xen emulates
>> instructions is if the memory operand is on a pagetable that's shadowed
>> (which might be a page that was recently a pagetable).
>>
>> 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
>
> Tim.
>
Tim, Thank you very much!
We were missing that cs and it solved problem.
--
Thanks,
Igor
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-10 13:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1306925044-2828-1-git-send-email-imammedo@redhat.com>
2011-06-01 12:39 ` [PATCH] memcg: do not expose uninitialized mem_cgroup_per_node to world Michal Hocko
2011-06-01 13:07 ` Igor Mammedov
2011-06-01 13:41 ` Michal Hocko
2011-06-01 14:39 ` Igor Mammedov
2011-06-01 15:20 ` Michal Hocko
2011-06-01 16:42 ` Igor Mammedov
2011-06-01 23:10 ` Hiroyuki Kamezawa
2011-06-03 12:35 ` Igor Mammedov
2011-06-03 13:00 ` Hiroyuki Kamezawa
2011-06-07 13:25 ` Igor Mammedov
2011-06-08 3:35 ` KAMEZAWA Hiroyuki
2011-06-08 21:09 ` Andrew Morton
2011-06-08 23:44 ` KAMEZAWA Hiroyuki
2011-06-10 16:57 ` Igor Mammedov
2011-07-26 21:17 ` Andrew Morton
2011-07-27 7:58 ` Michal Hocko
2011-07-27 9:30 ` Igor Mammedov
2011-07-27 9:57 ` Michal Hocko
2011-06-09 8:11 ` Igor Mammedov
2011-06-09 12:40 ` Possible shadow bug (was: Re: [PATCH] memcg: do not expose uninitialized mem_cgroup_per_node to world) Stefano Stabellini
2011-06-09 15:01 ` [Xen-devel] " Tim Deegan
2011-06-09 16:47 ` [Xen-devel] Possible shadow bug Igor Mammedov
2011-06-10 10:01 ` Tim Deegan
2011-06-10 10:10 ` Tim Deegan
2011-06-10 11:48 ` Pasi Kärkkäinen
2011-06-10 12:40 ` Tim Deegan
2011-06-10 15:38 ` Igor Mammedov
2011-06-10 13:55 ` Igor Mammedov [this message]
2011-06-01 13:49 ` [PATCH] memcg: do not expose uninitialized mem_cgroup_per_node to world Igor Mammedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF22245.20008@redhat.com \
--to=imammedo@redhat.com \
--cc=KAMEZAWA@phlegethon.org \
--cc=Stefano@phlegethon.org \
--cc=Tim.Deegan@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kamezawa.hiroyuki@gmail.com \
--cc=keir.xen@gmail.com \
--cc=keir@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mhocko@suse.cz \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).