From: Richard Weinberger <richard@nod.at>
To: linux-mtd@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hsiangkao@mail.ru, kirill.shutemov@linux.intel.com,
stable@vger.kernel.org, zhangjun <openzhangj@gmail.com>
Subject: Re: [PATCH] ubifs: Get/put page when changing PG_private
Date: Fri, 21 Dec 2018 09:56:25 +0100 [thread overview]
Message-ID: <386368225.TvJUPtmGVW@blindfold> (raw)
In-Reply-To: <20181215150130.19381-1-richard@nod.at>
Am Samstag, 15. Dezember 2018, 16:01:30 CET schrieb Richard Weinberger:
> The page migration code assumes that a page with PG_private
> set has its page count elevated by 1.
> UBIFS never did this and therefore the migration code was unable
> to migrate some pages owned by UBIFS.
> The lead to situations where the CMA memory allocator failed to
> allocate memory.
>
> Fix this by using get/put_page when changing PG_private.
>
> Cc: <stable@vger.kernel.org>
> Cc: zhangjun <openzhangj@gmail.com>
> Fixes: 4ac1c17b2044 ("UBIFS: Implement ->migratepage()")
> Reported-by: zhangjun <openzhangj@gmail.com>
> Signed-off-by: Richard Weinberger <richard@nod.at>
FYI, on the XFS side a similar change caused a regression.
https://marc.info/?l=linux-fsdevel&m=154530861202448&w=2
Until this regression is not fully understood, including the implications
for UBIFS, I'll not merge this patch.
Thanks,
//richard
next prev parent reply other threads:[~2018-12-21 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 15:01 [PATCH] ubifs: Get/put page when changing PG_private Richard Weinberger
2018-12-15 20:38 ` zhangjun
2018-12-17 10:59 ` Kirill A. Shutemov
2018-12-17 11:32 ` Richard Weinberger
2018-12-21 8:56 ` Richard Weinberger [this message]
2018-12-21 10:35 ` Kirill A. Shutemov
2018-12-25 2:42 ` zhangjun
2018-12-25 21:08 ` Richard Weinberger
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=386368225.TvJUPtmGVW@blindfold \
--to=richard@nod.at \
--cc=hsiangkao@mail.ru \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=openzhangj@gmail.com \
--cc=stable@vger.kernel.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).