From: David Hildenbrand <david@redhat.com>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
sonnyrao@chromium.org, yuzhao@google.com, rientjes@google.com
Subject: Re: [PATCH] Revert "mm/vmstat.c: do not show lowmem reserve protection information of empty zone"
Date: Tue, 11 Aug 2020 10:34:17 +0200 [thread overview]
Message-ID: <22a7882b-cc18-0c6d-1ab5-7e0ea6a53469@redhat.com> (raw)
In-Reply-To: <20200811075412.12872-1-bhe@redhat.com>
On 11.08.20 09:54, Baoquan He wrote:
> This reverts commit 26e7deadaae1755faf1f6d1a68988c4b8348df59.
>
> Sonny reported that one of their tests started failing on the latest
> kernel on their Chrome OS platform. The root cause is that the above
> commit removed the protection line of empty zone, while the parser used
> in the test relies on the protection line to mark the end of each zone.
>
> Let's revert it to avoid breaking userspace testing or applications.
>
> Cc: <stable@vger.kernel.org> # 5.8.x
> Reported-by: Sonny Rao <sonnyrao@chromium.org>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> mm/vmstat.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 5b35c0eb8c57..62376dc66ec0 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -1644,12 +1644,6 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,
> zone->present_pages,
> zone_managed_pages(zone));
>
> - /* If unpopulated, no other information is useful */
> - if (!populated_zone(zone)) {
> - seq_putc(m, '\n');
> - return;
> - }
> -
> seq_printf(m,
> "\n protection: (%ld",
> zone->lowmem_reserve[0]);
> @@ -1657,6 +1651,12 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,
> seq_printf(m, ", %ld", zone->lowmem_reserve[i]);
> seq_putc(m, ')');
>
> + /* If unpopulated, no other information is useful */
> + if (!populated_zone(zone)) {
> + seq_putc(m, '\n');
> + return;
> + }
> +
> for (i = 0; i < NR_VM_ZONE_STAT_ITEMS; i++)
> seq_printf(m, "\n %-12s %lu", zone_stat_name(i),
> zone_page_state(zone, i));
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-08-11 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 7:54 Baoquan He
2020-08-11 8:34 ` David Hildenbrand [this message]
2020-08-11 21:46 ` David Rientjes
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=22a7882b-cc18-0c6d-1ab5-7e0ea6a53469@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sonnyrao@chromium.org \
--cc=yuzhao@google.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