From: Sonny Rao <sonnyrao@chromium.org>
To: linux-mm@kvack.org
Cc: Yu Zhao <yuzhao@google.com>,
bhe@redhat.com, David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: ABI compatibility for /proc/zoneinfo
Date: Mon, 10 Aug 2020 14:24:03 -0700 [thread overview]
Message-ID: <CAPz6YkUD37dPeE+23QsyuPbT4iMMzeGOFeV9oTi87RuW2qsadA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
We (Chrome OS) noticed recently one of our tests started failing on
upstream kernels while parsing /proc/zoneinfo
I think this patch is the cause:
26e7deadaae17 mm/vmstat.c: do not show lowmem reserve protection
information of empty zone
Maybe our parser was being overly strict by looking for the protection
line, and it's not hard to fix but raised the question of whether there's
any ABI compatibility guarantees about these files?
[-- Attachment #2: Type: text/html, Size: 992 bytes --]
next reply other threads:[~2020-08-10 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 21:24 Sonny Rao [this message]
2020-08-10 21:46 ` Yu Zhao
2020-08-11 2:37 ` Baoquan He
2020-08-11 3:18 ` Sonny Rao
2020-08-11 3:58 ` Baoquan He
2020-08-11 4:01 ` Andrew Morton
2020-08-11 4:07 ` Baoquan He
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=CAPz6YkUD37dPeE+23QsyuPbT4iMMzeGOFeV9oTi87RuW2qsadA@mail.gmail.com \
--to=sonnyrao@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--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