From: Qian Cai <cai@lca.pw>
To: Cyril Hrubis <chrubis@suse.cz>,
linux-mm@kvack.org, linux-api@vger.kernel.org
Cc: ltp@lists.linux.it, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: mbind() fails to fail with EIO
Date: Mon, 18 Mar 2019 12:08:36 -0400 [thread overview]
Message-ID: <1552925316.26196.5.camel@lca.pw> (raw)
In-Reply-To: <20190315160142.GA8921@rei>
On Fri, 2019-03-15 at 17:01 +0100, Cyril Hrubis wrote:
> Hi!
> I've started to write tests for mbind() and found out that mbind() does
> not work as described in manual page in a case that page has been
> faulted on different node that we are asking it to bind to. Looks like
> this is working fine on older kernels. On my testing machine with 3.0
> mbind() fails correctly with EIO but succeeds unexpectedly on newer
> kernels such as 4.12.
>
> What the test does is:
>
> * mmap() private mapping
> * fault it
> * find out on which node it is faulted on
> * mbind() it to a different node with MPOL_BIND and MPOL_MF_STRICT and
> expects to get EIO
>
> The test code can be seen and compiled from:
>
> https://github.com/metan-ucw/ltp/blob/master/testcases/kernel/syscalls/mbind/m
> bind02.c
>
I am too lazy to checkout the repository and compile the whole thing just to be
able to reproduce. If you can make it a standalone program without LTP markups,
I'd be happy to take a look.
next prev parent reply other threads:[~2019-03-18 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 16:01 Cyril Hrubis
2019-03-18 16:08 ` Qian Cai [this message]
2019-03-19 12:59 ` Cyril Hrubis
2019-03-18 18:12 ` Yang Shi
2019-03-19 13:27 ` Oscar Salvador
2019-03-19 14:26 ` Kirill A. Shutemov
2019-03-19 14:30 ` Cyril Hrubis
2019-03-19 14:41 ` Oscar Salvador
2019-03-19 14:52 ` Kirill A. Shutemov
2019-03-19 15:10 ` Oscar Salvador
2019-03-19 16:29 ` Yang Shi
2019-03-19 16:25 ` Yang Shi
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=1552925316.26196.5.camel@lca.pw \
--to=cai@lca.pw \
--cc=chrubis@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ltp@lists.linux.it \
--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