From: Hugh Dickins <hughd@google.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix KPF_SWAPCACHE
Date: Wed, 8 Feb 2017 20:50:25 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1702082045430.1818@eggly.anvils> (raw)
In-Reply-To: <20170209142026.6861ffb0@roar.ozlabs.ibm.com>
On Thu, 9 Feb 2017, Nicholas Piggin wrote:
> On Tue, 7 Feb 2017 11:11:16 -0800 (PST)
> Hugh Dickins <hughd@google.com> wrote:
>
> > 4.10-rc1 commit 6326fec1122c ("mm: Use owner_priv bit for PageSwapCache,
> > valid when PageSwapBacked") aliased PG_swapcache to PG_owner_priv_1:
> > so /proc/kpageflags' KPF_SWAPCACHE should now be synthesized, instead
> > of being shown on unrelated pages which have PG_owner_priv_1 set.
> >
> > Signed-off-by: Hugh Dickins <hughd@google.com>
>
> Thanks Hugh, this seems fine to me. We want this for 4.10, no?
>
> Fixes: 6326fec1122c ("mm: Use owner_priv bit for PageSwapCache, valid when PageSwapBacked")
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Thanks Nick, yes, but don't worry: Linus jumped to it, and it's already
in 4.10 as b6789123bccb ("mm: fix KPF_SWAPCACHE in /proc/kpageflags").
Hugh
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-02-09 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 19:11 Hugh Dickins
2017-02-09 4:20 ` Nicholas Piggin
2017-02-09 4:50 ` Hugh Dickins [this message]
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=alpine.LSU.2.11.1702082045430.1818@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.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