From: "Kuan-Ying Lee (李冠穎)" <Kuan-Ying.Lee@mediatek.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "Andrew Yang (楊智強)" <Andrew.Yang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] mm/gup: Add folio to list when folio_isolate_lru() succeed
Date: Thu, 2 Feb 2023 02:13:55 +0000 [thread overview]
Message-ID: <ef92f5493f70cab6b09016c633395577c09bed1f.camel@mediatek.com> (raw)
In-Reply-To: <20230131151742.df43c3fd11bda01b613234ef@linux-foundation.org>
On Tue, 2023-01-31 at 15:17 -0800, Andrew Morton wrote:
> On Tue, 31 Jan 2023 14:32:06 +0800 Kuan-Ying Lee <
> Kuan-Ying.Lee@mediatek.com> wrote:
>
> > If we call folio_isolate_lru() successfully, we will get
> > return value 0. We need to add this folio to the
> > movable_pages_list.
> >
> > Fixes: 67e139b02d99 ("mm/gup.c: refactor
> > check_and_migrate_movable_pages()")
> > Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
> >
> > ...
> >
> > --- a/mm/gup.c
> > +++ b/mm/gup.c
> > @@ -1914,7 +1914,7 @@ static unsigned long
> > collect_longterm_unpinnable_pages(
> > drain_allow = false;
> > }
> >
> > - if (!folio_isolate_lru(folio))
> > + if (folio_isolate_lru(folio))
> > continue;
> >
> > list_add_tail(&folio->lru, movable_page_list);
>
> Thanks. What are the user-visible effects of this bug?
Hi Andrew,
I didn't hit bug on real devices. I observe this issue
by tracing get_user_pages() call flow.
Thanks.
next prev parent reply other threads:[~2023-02-02 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 6:32 Kuan-Ying Lee
2023-01-31 23:17 ` Andrew Morton
2023-02-02 2:13 ` Kuan-Ying Lee (李冠穎) [this message]
2023-02-02 6:09 ` Alistair Popple
2023-02-01 9:08 ` Baolin Wang
2023-02-02 8:39 ` David Hildenbrand
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=ef92f5493f70cab6b09016c633395577c09bed1f.camel@mediatek.com \
--to=kuan-ying.lee@mediatek.com \
--cc=Andrew.Yang@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=chinwen.chang@mediatek.com \
--cc=jhubbard@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.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