From: Michal Hocko <mhocko@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] [RFC] syscalls/mmap12: Do not fail on non-present pages
Date: Fri, 18 Aug 2017 15:50:35 +0200 [thread overview]
Message-ID: <20170818135035.GD18499@dhcp22.suse.cz> (raw)
In-Reply-To: <1932775025.3810596.1503050454745.JavaMail.zimbra@redhat.com>
On Fri 18-08-17 06:00:54, Jan Stancek wrote:
[...]
> @Michal: Can you think of alternative way to differentiate between:
> "MAP_POPULATE did its best" vs. "MAP_POPULATE is broken"?
What about reading /proc/self/smaps for the range and check for RSS
field? Seeing 0 could be reported as an unexpected _warning_ but I am
not really sure there is any correctness test we could do here. Maybe
just compare that MAP_POPULATE will give you the same content as the
manual fault in.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-08-18 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:33 [LTP] [PATCH 1/2] [COMMITTED] syscalls/mmap12: Convert to the new library Cyril Hrubis
2017-08-17 14:33 ` [LTP] [PATCH 2/2] [RFC] syscalls/mmap12: Do not fail on non-present pages Cyril Hrubis
2017-08-18 10:00 ` Jan Stancek
2017-08-18 13:50 ` Michal Hocko [this message]
2017-09-14 11:44 ` Cyril Hrubis
2017-09-14 14:08 ` Jan Stancek
2017-09-14 15:05 ` Cyril Hrubis
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=20170818135035.GD18499@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=ltp@lists.linux.it \
/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