From: Cyril Hrubis <chrubis@suse.cz>
To: Carmelo Amoroso <carmelo.amoroso@st.com>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] MAP_LOCKED issue in mmap with MAP_ANYNOMOUS
Date: Mon, 23 Mar 2015 07:53:53 +0100 [thread overview]
Message-ID: <20150323065353.GC3618@rei> (raw)
In-Reply-To: <20150322064333.GM4504@vapier>
Hi!
> > So, should the LTP be updated accordingly ?
>
> if the kernel has changed behavior, LTP needs to adapt to it (assuming the
> kernel people changed the behavior on purpose)
The kernel contradicts the manual page here and the change was
unintentional, it's side effect from fixes for deadlock.
Michal Hocko was looking into the issue, he said that they will likely
discuss it on LSMM. I will ask him if they agreed on what should be done
about it.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2015-03-23 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 5:28 [LTP] MAP_LOCKED issue in mmap with MAP_ANYNOMOUS Satish Gedela
2015-03-20 8:11 ` Jan Stancek
2015-03-20 11:42 ` Satish Gedela
2015-03-20 13:13 ` Jan Stancek
2015-03-20 14:06 ` Carmelo Amoroso
2015-03-22 6:43 ` Mike Frysinger
2015-03-23 6:53 ` Cyril Hrubis [this message]
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=20150323065353.GC3618@rei \
--to=chrubis@suse.cz \
--cc=carmelo.amoroso@st.com \
--cc=ltp-list@lists.sourceforge.net \
/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