From: Shakeel Butt <shakeelb@google.com>
To: Henry Burns <henryburns@google.com>
Cc: Vitaly Vul <vitaly.vul@sony.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Adams <jwadams@google.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/z3fold.c: Reinitialize zhdr structs after migration
Date: Tue, 16 Jul 2019 14:20:28 -0700 [thread overview]
Message-ID: <CALvZod46LCSyCJEuBr_0yLjAbg_fJc+qr9-NNU5mbio8mqM1ag@mail.gmail.com> (raw)
In-Reply-To: <20190716000520.230595-1-henryburns@google.com>
On Mon, Jul 15, 2019 at 5:05 PM Henry Burns <henryburns@google.com> wrote:
>
> z3fold_page_migration() calls memcpy(new_zhdr, zhdr, PAGE_SIZE).
> However, zhdr contains fields that can't be directly coppied over (ex:
> list_head, a circular linked list). We only need to initialize the
> linked lists in new_zhdr, as z3fold_isolate_page() already ensures
> that these lists are empty
>
> Additionally it is possible that zhdr->work has been placed in a
> workqueue. In this case we shouldn't migrate the page, as zhdr->work
> references zhdr as opposed to new_zhdr.
>
> Fixes: bba4c5f96ce4 ("mm/z3fold.c: support page migration")
> Signed-off-by: Henry Burns <henryburns@google.com>
Reviewed-by: Shakeel Butt <shakeelb@google.com>
> ---
> Changelog since v1:
> - Made comments explicityly refer to new_zhdr->buddy.
>
> mm/z3fold.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/mm/z3fold.c b/mm/z3fold.c
> index 42ef9955117c..f4b2283b19a3 100644
> --- a/mm/z3fold.c
> +++ b/mm/z3fold.c
> @@ -1352,12 +1352,22 @@ static int z3fold_page_migrate(struct address_space *mapping, struct page *newpa
> z3fold_page_unlock(zhdr);
> return -EBUSY;
> }
> + if (work_pending(&zhdr->work)) {
> + z3fold_page_unlock(zhdr);
> + return -EAGAIN;
> + }
> new_zhdr = page_address(newpage);
> memcpy(new_zhdr, zhdr, PAGE_SIZE);
> newpage->private = page->private;
> page->private = 0;
> z3fold_page_unlock(zhdr);
> spin_lock_init(&new_zhdr->page_lock);
> + INIT_WORK(&new_zhdr->work, compact_page_work);
> + /*
> + * z3fold_page_isolate() ensures that new_zhdr->buddy is empty,
> + * so we only have to reinitialize it.
> + */
> + INIT_LIST_HEAD(&new_zhdr->buddy);
> new_mapping = page_mapping(page);
> __ClearPageMovable(page);
> ClearPagePrivate(page);
> --
> 2.22.0.510.g264f2c817a-goog
>
prev parent reply other threads:[~2019-07-16 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 0:05 Henry Burns
2019-07-16 21:20 ` Shakeel Butt [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=CALvZod46LCSyCJEuBr_0yLjAbg_fJc+qr9-NNU5mbio8mqM1ag@mail.gmail.com \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=henryburns@google.com \
--cc=jwadams@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vitaly.vul@sony.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