From: Minchan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Lee Schermerhorn <lee.schermerhorn@hp.com>
Subject: Re: [PATCH] Check PageActive when evictable page and unevicetable page race happen
Date: Sun, 24 Apr 2011 14:50:58 +0900 [thread overview]
Message-ID: <20110424055058.GA1826@barrios-desktop> (raw)
In-Reply-To: <BANLkTimzg184ZWraBomJ8ex1-B4Ypj6D9Q@mail.gmail.com>
Hi KOSAKI,
On Sun, Apr 24, 2011 at 12:02:57PM +0900, KOSAKI Motohiro wrote:
> 2011/4/24 Minchan Kim <minchan.kim@gmail.com>:
> > In putback_lru_page, unevictable page can be changed into evictable
> > 's one while we move it among lru. So we have checked it again and
> > rescued it. But we don't check PageActive, again. It could add
> > active page into inactive list so we can see the BUG in isolate_lru_pages.
> > (But I didn't see any report because I think it's very subtle)
> >
> > It could happen in race that zap_pte_range's mark_page_accessed and
> > putback_lru_page. It's subtle but could be possible.
> >
> > Note:
> > While I review the code, I found it. So it's not real report.
> >
> > Cc: Rik van Riel <riel@redhat.com>
> > Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > Cc: Hugh Dickins <hughd@google.com>
> > Cc: Johannes Weiner <hannes@cmpxchg.org>
> > Cc: Lee Schermerhorn <lee.schermerhorn@hp.com>
> > Signed-off-by: Minchan Kim <minchan.kim@gmail.com>
> > ---
> > mm/vmscan.c | 4 +++-
> > 1 files changed, 3 insertions(+), 1 deletions(-)
> >
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index b3a569f..c0cd1aa 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -562,7 +562,7 @@ int remove_mapping(struct address_space *mapping, struct page *page)
> > void putback_lru_page(struct page *page)
> > {
> > int lru;
> > - int active = !!TestClearPageActive(page);
> > + int active;
> > int was_unevictable = PageUnevictable(page);
> >
> > VM_BUG_ON(PageLRU(page));
> > @@ -571,6 +571,7 @@ redo:
> > ClearPageUnevictable(page);
> >
> > if (page_evictable(page, NULL)) {
> > + active = !!TestClearPageActive(page);
> > /*
> > * For evictable pages, we can use the cache.
> > * In event of a race, worst case is we end up with an
> > @@ -584,6 +585,7 @@ redo:
> > * Put unevictable pages directly on zone's unevictable
> > * list.
> > */
> > + ClearPageActive(page);
> > lru = LRU_UNEVICTABLE;
> > add_page_to_unevictable_list(page);
>
> I think we forgot 'goto redo' case. following patch is better?
>
> ------------------------------------------------
> if (page_evictable(page, NULL)) {
> /*
> * For evictable pages, we can use the cache.
> * In event of a race, worst case is we end up with an
> * unevictable page on [in]active list.
> * We know how to handle that.
> */
> lru = active + page_lru_base_type(page);
> + if (active)
> + SetPageActive(page);
> lru_cache_add_lru(page, lru);
PageActive is reset by lru_cache_add_lru so it's meaningless.
BTW, please ignore this patch. :)
I think LRU status of isolated page cannot be changed.
Thanks for the review.
--
Kind regards,
Minchan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-24 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 0:25 Minchan Kim
2011-04-24 2:01 ` Minchan Kim
2011-04-24 3:02 ` KOSAKI Motohiro
2011-04-24 5:50 ` Minchan Kim [this message]
2011-04-24 5:37 ` Minchan Kim
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=20110424055058.GA1826@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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