xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/mm/shadow: spurious warning when unmapping xenheap pages.
Date: Fri, 5 Apr 2013 11:40:23 +0100	[thread overview]
Message-ID: <515EAA17.7050609@citrix.com> (raw)
In-Reply-To: <20130405084602.GB55764@ocelot.phlegethon.org>

On 05/04/13 09:46, Tim Deegan wrote:
> At 09:37 +0100 on 05 Apr (1365154638), Jan Beulich wrote:
>>>>> On 05.04.13 at 10:30, Tim Deegan <tim@xen.org> wrote:
>>> At 09:11 +0100 on 05 Apr (1365153095), Jan Beulich wrote:
>>>>>>> On 28.03.13 at 11:35, Tim Deegan <tim@xen.org> wrote:
>>>>> Xenheap pages will always have an extra typecount, taken in
>>>>> share_xen_page_with_guest(), which doesn't come from a shadow PTE.
>>>>> Adjust the warning in sh_remove_all_mappings() to account for it.
>>>>>
>>>>> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>> Signed-off-by: Tim Deegan <tim@xen.org>
>>>> I suppose this ought to go into 4.2.2 and 4.1.5 as well?
>>> Could do -- it's just suppressing a printk, so not a particularly urgent
>>> fix AFAICT.
>> But the message, if present when inspecting some random log,
>> looks worrying, so getting rid of the false positive is likely going
>> to help assessing the health of systems/guests.
> Sure.  In any case the patch is harmless, so there should be no risk to
> putting it in.
>
> Tim.

The reason I started debugging it was because it is an scary message for
what turns out to be a safe action.

So please backport :)

~Andrew

>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2013-04-05 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 10:35 [PATCH] x86/mm/shadow: spurious warning when unmapping xenheap pages Tim Deegan
2013-04-02 10:09 ` Andrew Cooper
2013-04-05  8:11 ` Jan Beulich
2013-04-05  8:30   ` Tim Deegan
2013-04-05  8:37     ` Jan Beulich
2013-04-05  8:46       ` Tim Deegan
2013-04-05 10:40         ` Andrew Cooper [this message]

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=515EAA17.7050609@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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).