From: Michal Hocko <mhocko@kernel.org>
To: akpm@linux-foundation.org
Cc: apolyakov@beget.ru, apolyakov@beget.com,
mgorman@techsingularity.net, vbabka@suse.cz,
mm-commits@vger.kernel.org, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: + fix-print-order-in-show_free_areas.patch added to -mm tree
Date: Tue, 4 Apr 2017 10:57:26 +0200 [thread overview]
Message-ID: <20170404085725.GF15132@dhcp22.suse.cz> (raw)
In-Reply-To: <58e2c885.fYYyNuCxKh7sHx78%akpm@linux-foundation.org>
JFTR. Joe, has already noticed this
http://lkml.kernel.org/r/2aaf6f1701ee78582743d91359018689d5826e82.1489628459.git.joe@perches.com
and I have requested to split out the fix from the rest of the
whitespace noise
http://lkml.kernel.org/r/20170316105733.GC30508@dhcp22.suse.cz
but Joe hasn't really followed up and I didn't get to do it myself.
On Mon 03-04-17 15:11:17, Andrew Morton wrote:
> From: Alexander Polakov <apolyakov@beget.ru>
> Subject: mmpage_alloc.c: fix print order in show_free_areas()
>
> Fixes: 11fb998986a72a ("mm: move most file-based accounting to the node")
> Link: http://lkml.kernel.org/r/1490377730.30219.2.camel@beget.ru
> Signed-off-by: Alexander Polyakov <apolyakov@beget.com>
> Cc: Mel Gorman <mgorman@techsingularity.net>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> Cc: Michal Hocko <mhocko@suse.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Even though this cannot cause any crash or misbehaving it is still
confusing enough to be worth backporting to stable
Cc: stable # 4.8+
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
>
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN mm/page_alloc.c~fix-print-order-in-show_free_areas mm/page_alloc.c
> --- a/mm/page_alloc.c~fix-print-order-in-show_free_areas
> +++ a/mm/page_alloc.c
> @@ -4519,13 +4519,13 @@ void show_free_areas(unsigned int filter
> K(node_page_state(pgdat, NR_FILE_MAPPED)),
> K(node_page_state(pgdat, NR_FILE_DIRTY)),
> K(node_page_state(pgdat, NR_WRITEBACK)),
> + K(node_page_state(pgdat, NR_SHMEM)),
> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> K(node_page_state(pgdat, NR_SHMEM_THPS) * HPAGE_PMD_NR),
> K(node_page_state(pgdat, NR_SHMEM_PMDMAPPED)
> * HPAGE_PMD_NR),
> K(node_page_state(pgdat, NR_ANON_THPS) * HPAGE_PMD_NR),
> #endif
> - K(node_page_state(pgdat, NR_SHMEM)),
> K(node_page_state(pgdat, NR_WRITEBACK_TEMP)),
> K(node_page_state(pgdat, NR_UNSTABLE_NFS)),
> node_page_state(pgdat, NR_PAGES_SCANNED),
> _
>
> Patches currently in -mm which might be from apolyakov@beget.ru are
>
> fix-print-order-in-show_free_areas.patch
>
--
Michal Hocko
SUSE Labs
--
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>
parent reply other threads:[~2017-04-04 8:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <58e2c885.fYYyNuCxKh7sHx78%akpm@linux-foundation.org>]
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=20170404085725.GF15132@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apolyakov@beget.com \
--cc=apolyakov@beget.ru \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mm-commits@vger.kernel.org \
--cc=vbabka@suse.cz \
/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