From: Rafael David Tinoco <rafael.tinoco@linaro.org>
To: Sasha Levin <sashal@kernel.org>, linux-mm@kvack.org
Cc: Rafael David Tinoco <rafael.tinoco@linaro.org>,
gregkh@linuxfoundation.org, stable@vger.kernel.org,
kirill.shutemov@linux.intel.com, wei.guo.simon@gmail.com,
akpm@linux-foundation.org
Subject: Re: stable request: mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT)
Date: Thu, 29 Nov 2018 14:32:30 -0200 [thread overview]
Message-ID: <d6077494-79d9-c0b0-4264-4121a47406b5@linaro.org> (raw)
In-Reply-To: <20181108172557.GE8097@sasha-vm>
On 11/8/18 3:25 PM, Sasha Levin wrote:
> + linux-mm@
Thanks Sasha,
>
> This is actually upstream commit
> b155b4fde5bdde9fed439cd1f5ea07173df2ed31.
>
> On Thu, Nov 08, 2018 at 08:07:35AM -0200, Rafael David Tinoco wrote:
>> Hello Greg,
>>
>> Could you please consider backporting to v4.4 the following commit:
>>
>> commit b5b5b6fe643391209b08528bef410e0cf299b826
>> Author: Simon Guo <wei.guo.simon@gmail.com>
>> Date: Fri Oct 7 20:59:40 2016
>>
>> mm: mlock: avoid increase mm->locked_vm on mlock() when already
>> mlock2(,MLOCK_ONFAULT)
>>
>> It seems to be a trivial fix for:
>>
>> https://bugs.linaro.org/show_bug.cgi?id=4043
>> (mlock203.c LTP test failing on v4.4)
>>
ping ?
Related bug: https://bugs.linaro.org/show_bug.cgi?id=4043
v4.4 only.
Thank you!
--
Rafael D. Tinoco
Linaro Kernel Validation
prev parent reply other threads:[~2018-11-29 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABdQkv_qGi7x4mQjH_mwGGnJs9F85CETOv9HLv=xvQVSPL_N3Q@mail.gmail.com>
2018-11-08 17:25 ` stable request: mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT) Sasha Levin
2018-11-29 16:32 ` Rafael David Tinoco [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=d6077494-79d9-c0b0-4264-4121a47406b5@linaro.org \
--to=rafael.tinoco@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wei.guo.simon@gmail.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;
as well as URLs for NNTP newsgroup(s).