linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Michel Lespinasse <walken@google.com>
Cc: Hugh Dickins <hughd@google.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: huge zero page vs FOLL_DUMP
Date: Sat, 12 Jan 2013 05:36:59 +0200	[thread overview]
Message-ID: <20130112033659.GA26890@otc-wbsnb-06> (raw)
In-Reply-To: <CANN689E5iw=UHfG1r82c91cZVqhX9xrxttKw3SCy=ZSgcAicNQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]

On Fri, Jan 11, 2013 at 03:53:34PM -0800, Michel Lespinasse wrote:
> Hi,
> 
> follow_page() has code to return ERR_PTR(-EFAULT) when it encounters
> the zero page and FOLL_DUMP flag is passed - this is used to avoid
> dumping the zero page to disk when doing core dumps, and also by
> munlock to avoid having potentially large number of threads trying to
> munlock the zero page at once, which we can't reclaim anyway.
> 
> We don't have the corresponding logic when follow_page() encounters a
> huge zero page. I think we should, preferably before 3.8. However, I
> am slightly confused as to what to do for the munlock case, as the
> huge zero page actually does seem to be reclaimable. My guess is that
> we could still skip the munlocks, until the zero page is actually
> reclaimed at which point we should check if we can munlock it.
> 
> Kirill, is this something you would have time to look into ?

Nice catch! Thank you.

I don't think we should do anything about mlock(). Huge zero page cannot
be mlocked -- it will not pass page->mapping check in
follow_trans_huge_pmd(). And it's not reclaimable if it's mapped to
anywhere.

Could you tese the patch?

From 062a9b670ede9fe5fca1d1947b42990b6b0642a4 Mon Sep 17 00:00:00 2001
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Date: Sat, 12 Jan 2013 05:18:58 +0200
Subject: [PATCH] thp: Avoid dumping huge zero page

No reason to preserve huge zero page in core dump.

Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reported-by: Michel Lespinasse <walken@google.com>
---
 mm/huge_memory.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 6001ee6..b5783d8 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -1257,6 +1257,10 @@ struct page *follow_trans_huge_pmd(struct vm_area_struct *vma,
 	if (flags & FOLL_WRITE && !pmd_write(*pmd))
 		goto out;
 
+	/* Avoid dumping huge zero page */
+	if ((flags & FOLL_DUMP) && is_huge_zero_pmd(*pmd))
+		return ERR_PTR(-EFAULT);
+
 	page = pmd_page(*pmd);
 	VM_BUG_ON(!PageHead(page));
 	if (flags & FOLL_TOUCH) {
-- 
1.8.1

-- 
 Kirill A. Shutemov

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-12  3:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 23:53 huge zero page vs FOLL_DUMP Michel Lespinasse
2013-01-12  3:36 ` Kirill A. Shutemov [this message]
2013-01-12  4:27   ` Michel Lespinasse
2013-01-14 15:18     ` Kirill A. Shutemov
2013-01-13  1:43   ` Simon Jeons
2013-01-13 16:10     ` Kirill A. Shutemov

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=20130112033659.GA26890@otc-wbsnb-06 \
    --to=kirill.shutemov@linux.intel.com \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=walken@google.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).