linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Richard Weinberger <richard@nod.at>
Cc: zhangjun <openzhangj@gmail.com>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	kirill.shutemov@linux.intel.com, hch@lst.de,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] ubifs: fix page_count in ->ubifs_migrate_page()
Date: Fri, 14 Dec 2018 01:00:00 +0300	[thread overview]
Message-ID: <20181213220000.7b56wysed67y5iv6@kshutemo-mobl1> (raw)
In-Reply-To: <8239265.3QN2sXB6kY@blindfold>

On Thu, Dec 13, 2018 at 10:36:47PM +0100, Richard Weinberger wrote:
> Am Donnerstag, 13. Dezember 2018, 20:20:17 CET schrieb zhangjun:
> > Because the PagePrivate() in UBIFS is different meanings,
> 
> ...has different meanings...
> 
> I'll fix up that myself after applying your patch. No need to send a v3.
> 
> > alloc_cma() will fail when one dirty page cache located in
> > the type of MIGRATE_CMA
> > 
> > If not adjust the 'extra_count' for dirty page,
> > ubifs_migrate_page() -> migrate_page_move_mapping() will
> > always return -EAGAIN for:
> > 	expected_count += page_has_private(page)
> > This causes the migration to fail until the page cache is cleaned
> > 
> > In general, PagePrivate() indicates that buff_head is already bound
> > to this page, and at the same time page_count() will also increase.
> > But UBIFS set private flag when the cache is dirty, and page_count()
> > not increase.
> > Therefore, the expected_count of UBIFS is different from the general
> > case.
> > 
> > Signed-off-by: zhangjun <openzhangj@gmail.com>
> 
> Fixes: 4ac1c17b2044 ("UBIFS: Implement ->migratepage()")
> 
> > ---
> >  fs/ubifs/file.c | 11 ++++++++++-
> >  1 file changed, 10 insertions(+), 1 deletion(-)
> > 
> > diff --git a/fs/ubifs/file.c b/fs/ubifs/file.c
> > index 1b78f2e..890dfce 100644
> > --- a/fs/ubifs/file.c
> > +++ b/fs/ubifs/file.c
> > @@ -1480,8 +1480,17 @@ static int ubifs_migrate_page(struct address_space *mapping,
> >  		struct page *newpage, struct page *page, enum migrate_mode mode)
> >  {
> >  	int rc;
> > +	int extra_count = 0;
> >  
> > -	rc = migrate_page_move_mapping(mapping, newpage, page, NULL, mode, 0);
> > +	/*
> > +	 * UBIFS uses PG_private as marker and does not raise the page counter.
> > +	 * migrate_page_move_mapping() expects a incremented counter if
> > +	 * PG_private is set. Therefore pass -1 as extra_count for this case.
> > +	 */
> > +	if (page_has_private(page))
> > +		extra_count = -1;
> > +	rc = migrate_page_move_mapping(mapping, newpage, page,
> > +			NULL, mode, extra_count);
> >  	if (rc != MIGRATEPAGE_SUCCESS)
> >  		return rc;
> >  
> 
> Let's wait a few days to give Kirill a chance to review, then I'll apply the patch.

I don't remmeber much context now...

Could you remind me why ubifs doesn't take additional pin when sets
PG_private?

Migration is not the only place where the additional pin is implied.
See all users of page_has_private() helper. Notably reclaim path.

-- 
 Kirill A. Shutemov

  reply	other threads:[~2018-12-13 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1544728817-2870-1-git-send-email-openzhangj@gmail.com>
2018-12-13 21:36 ` [PATCH v2] ubifs: fix page_count in ->ubifs_migrate_page() Richard Weinberger
2018-12-13 22:00   ` Kirill A. Shutemov [this message]
2018-12-13 22: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=20181213220000.7b56wysed67y5iv6@kshutemo-mobl1 \
    --to=kirill@shutemov.name \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hch@lst.de \
    --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=richard@nod.at \
    /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).