From: Henry Burns <henryburns@google.com>
To: Vitaly Wool <vitalywool@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vitaly Vul <vitaly.vul@sony.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Xidong Wang <wangxidong_97@163.com>,
Shakeel Butt <shakeelb@google.com>,
Jonathan Adams <jwadams@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Henry Burns <henryburns@google.com>
Subject: [PATCH v2] mm/z3fold.c: Lock z3fold page before __SetPageMovable()
Date: Mon, 1 Jul 2019 17:51:22 -0700 [thread overview]
Message-ID: <20190702005122.41036-1-henryburns@google.com> (raw)
__SetPageMovable() expects it's page to be locked, but z3fold.c doesn't
lock the page. Following zsmalloc.c's example we call trylock_page() and
unlock_page(). Also makes z3fold_page_migrate() assert that newpage is
passed in locked, as documentation.
Signed-off-by: Henry Burns <henryburns@google.com>
Suggested-by: Vitaly Wool <vitalywool@gmail.com>
---
Changelog since v1:
- Added an if statement around WARN_ON(trylock_page(page)) to avoid
unlocking a page locked by a someone else.
mm/z3fold.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/mm/z3fold.c b/mm/z3fold.c
index e174d1549734..6341435b9610 100644
--- a/mm/z3fold.c
+++ b/mm/z3fold.c
@@ -918,7 +918,10 @@ static int z3fold_alloc(struct z3fold_pool *pool, size_t size, gfp_t gfp,
set_bit(PAGE_HEADLESS, &page->private);
goto headless;
}
- __SetPageMovable(page, pool->inode->i_mapping);
+ if (!WARN_ON(!trylock_page(page))) {
+ __SetPageMovable(page, pool->inode->i_mapping);
+ unlock_page(page);
+ }
z3fold_page_lock(zhdr);
found:
@@ -1325,6 +1328,7 @@ static int z3fold_page_migrate(struct address_space *mapping, struct page *newpa
VM_BUG_ON_PAGE(!PageMovable(page), page);
VM_BUG_ON_PAGE(!PageIsolated(page), page);
+ VM_BUG_ON_PAGE(!PageLocked(newpage), newpage);
zhdr = page_address(page);
pool = zhdr_to_pool(zhdr);
--
2.22.0.410.gd8fdbe21b5-goog
next reply other threads:[~2019-07-02 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 0:51 Henry Burns [this message]
2019-07-02 1:00 ` Shakeel Butt
2019-07-02 1:16 ` Henry Burns
2019-07-02 21:19 ` Andrew Morton
2019-07-02 22:17 ` Henry Burns
2019-07-02 22:24 ` Andrew Morton
2019-07-03 5:53 ` Vitaly Wool
2019-07-03 16:39 ` Henry Burns
2019-07-03 5:54 ` Vitaly Wool
2019-07-02 9:53 ` Vitaly Wool
2019-07-02 18:58 ` David Rientjes
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=20190702005122.41036-1-henryburns@google.com \
--to=henryburns@google.com \
--cc=akpm@linux-foundation.org \
--cc=jwadams@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=shakeelb@google.com \
--cc=vitaly.vul@sony.com \
--cc=vitalywool@gmail.com \
--cc=wangxidong_97@163.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