All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: (XEN) Xen BUG at page_alloc.c:385
Date: Wed, 20 Oct 2010 10:50:43 +0200	[thread overview]
Message-ID: <201010201050.44210.dietmar.hahn@ts.fujitsu.com> (raw)
In-Reply-To: <4CBDBDEE020000780001E053@vpn.id2.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]

Am 19.10.2010 schrieb "Jan Beulich <JBeulich@novell.com>":
> >>> On 19.10.10 at 14:16, Dietmar Hahn <dietmar.hahn@ts.fujitsu.com> wrote:
> > (XEN) Xen BUG at page_alloc.c:385
> > 
> >     The code line is:
> >         BUG_ON(pg[i].count_info != PGC_state_free);
> >     Is it possible in any way that a free page is in use? Or is it always a
> >     failure somewhere in the code like a multiple use of the same page?
> 
> Free pages are never in use for anything, so getting this BUG_ON()
> to trigger means e.g. something modified a page's state after it was
> already passed back to the allocator.
> 
> Did you check that this is not another manifestation of the problem
> fixed by c/s 22135 (we have a backport of this in our tree, but it's
> not clear whether yours already has this).

Sorry I wasn't aware of this fix and the backport is not in our source.
Thanks.

Dietmar.

> 
> Jan

-- 
Company details: http://ts.fujitsu.com/imprint.html

[-- Attachment #1.2: Type: text/html, Size: 5276 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-10-20  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 12:16 (XEN) Xen BUG at page_alloc.c:385 Dietmar Hahn
2010-10-19 13:49 ` Jan Beulich
2010-10-20  8:50   ` Dietmar Hahn [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=201010201050.44210.dietmar.hahn@ts.fujitsu.com \
    --to=dietmar.hahn@ts.fujitsu.com \
    --cc=JBeulich@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.