From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: "boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"JBeulich@suse.com" <JBeulich@suse.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
George Dunlap <George.Dunlap@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"julien.grall@arm.com" <julien.grall@arm.com>
Subject: Re: [PATCH] mm/page_alloc: correct first_dirty calculations during block merging
Date: Wed, 11 Jul 2018 07:47:46 +0000 [thread overview]
Message-ID: <98a3491ce0346d1e122a4f5a20ea99d88563e3d9.camel@citrix.com> (raw)
In-Reply-To: <4fc384f5-79b0-ffdc-e07a-3a5ec4b76a7b@oracle.com>
On Tue, 2018-07-10 at 11:34 -0400, Boris Ostrovsky wrote:
> On 07/10/2018 11:15 AM, Jan Beulich wrote:
> > > > > On 10.07.18 at 16:49, <sergey.dyasli@citrix.com> wrote:
> > >
> > > Currently it's possible to hit an assertion in alloc_heap_pages():
> > >
> > > Assertion 'first_dirty != INVALID_DIRTY_IDX || !(pg[i].count_info &
> > > PGC_need_scrub)' failed at page_alloc.c:988
> > >
> > > This can happen because a piece of logic to calculate first_dirty
> > > during block merging in free_heap_pages() is missing for the following
> > > scenario:
> > >
> > > 1. Current block's first_dirty equals to INVALID_DIRTY_IDX
> > > 2. Successor block is free but its first_dirty != INVALID_DIRTY_IDX
> > > 3. The successor is merged into current block
> > > 4. Current block's first_dirty still equals to INVALID_DIRTY_IDX
> > >
> > > This will trigger the assertion during allocation of such block in
> > > alloc_heap_pages() because there will be pages with PGC_need_scrub
> > > bit set despite the claim of first_dirty that the block is scrubbed.
> > >
> > > Add the missing piece of logic and slightly update the comment for
> > > the predecessor case to better capture the code's intent.
> > >
> > > Fixes 1a37f33ea613 ("mm: Place unscrubbed pages at the end of pagelist")
> > >
> > > Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
> > > ---
> > > CC: Andrew Cooper <andrew.cooper3@citrix.com>
> > > CC: George Dunlap <George.Dunlap@eu.citrix.com>
> > > CC: Jan Beulich <jbeulich@suse.com>
> > > CC: Julien Grall <julien.grall@arm.com>
> > > CC: Wei Liu <wei.liu2@citrix.com>
> > > CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> > > ---
> > > xen/common/page_alloc.c | 8 +++++++-
> > > 1 file changed, 7 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
> > > index 20ee1e4897..aa911f2dc5 100644
> > > --- a/xen/common/page_alloc.c
> > > +++ b/xen/common/page_alloc.c
> > > @@ -1426,7 +1426,7 @@ static void free_heap_pages(
> > >
> > > page_list_del(predecessor, &heap(node, zone, order));
> > >
> > > - /* Keep predecessor's first_dirty if it is already set. */
> > > + /* Keep block's first_dirty if the predecessor doesn't have one */
> > > if ( predecessor->u.free.first_dirty == INVALID_DIRTY_IDX &&
> > > pg->u.free.first_dirty != INVALID_DIRTY_IDX )
> > > predecessor->u.free.first_dirty = (1U << order) +
> >
> > How about "Convert pg's first_dirty if predecessor doesn't already have
> > one"? "Keep" isn't describing well enough what's being done here imo.
>
> "Keep" was used here for the (not provided) "else" clause. But I can see
> how it can be confusing.
>
> "Update predecessor's first_dirty if necessary"? Or maybe even drop it.
I'd like to retain the comments. Personally, I like the following
variant because the if statement logic is pretty self-explanatory:
/* Update predecessor's first_dirty if necessary */
...
/* Update pg's first_dirty if necessary */
These changes can be done while committing.
--
Thanks,
Sergey
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-07-11 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 14:49 [PATCH] mm/page_alloc: correct first_dirty calculations during block merging Sergey Dyasli
2018-07-10 15:15 ` Jan Beulich
2018-07-10 15:34 ` Boris Ostrovsky
2018-07-11 7:47 ` Sergey Dyasli [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=98a3491ce0346d1e122a4f5a20ea99d88563e3d9.camel@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=julien.grall@arm.com \
--cc=wei.liu2@citrix.com \
--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).