From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCH 0/2] THP mlock fix
Date: Tue, 29 Dec 2015 23:46:28 +0300 [thread overview]
Message-ID: <1451421990-32297-1-git-send-email-kirill.shutemov@linux.intel.com> (raw)
Hi Andrew,
There are two patches below. I believe either of the would fix the bug
reported by Sasha, but it worth applying both.
Sasha, as I cannot trigger the bug, I would like to have your Tested-by.
Kirill A. Shutemov (2):
mm, oom: skip mlocked VMAs in __oom_reap_vmas()
mm, thp: clear PG_mlocked when last mapping gone
mm/oom_kill.c | 7 +++++++
mm/rmap.c | 3 +++
2 files changed, 10 insertions(+)
--
2.6.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-12-29 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 20:46 Kirill A. Shutemov [this message]
2015-12-29 20:46 ` [PATCH 1/2] mm, oom: skip mlocked VMAs in __oom_reap_vmas() Kirill A. Shutemov
2016-01-05 12:47 ` Michal Hocko
2016-01-05 13:10 ` Kirill A. Shutemov
2016-01-05 13:31 ` Michal Hocko
2016-01-05 15:03 ` Kirill A. Shutemov
2016-01-05 15:45 ` Michal Hocko
2016-01-05 13:33 ` Michal Hocko
2016-01-05 15:03 ` Kirill A. Shutemov
2016-01-05 15:44 ` Sasha Levin
2015-12-29 20:46 ` [PATCH 2/2] mm, thp: clear PG_mlocked when last mapping gone Kirill A. Shutemov
2016-01-05 9:37 ` Vlastimil Babka
2016-01-05 14:37 ` Kirill A. Shutemov
2015-12-29 20:52 ` [PATCH 0/2] THP mlock fix Sasha Levin
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=1451421990-32297-1-git-send-email-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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