All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Sasha Levin <sasha.levin@oracle.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	shli@kernel.org, Hugh Dickins <hughd@google.com>,
	Rik van Riel <riel@redhat.com>, Shaohua Li <shli@fusionio.com>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [patch 019/154] mm: make madvise(MADV_WILLNEED) support swap file prefetch
Date: Mon, 23 Dec 2013 12:54:29 +0200 (EET)	[thread overview]
Message-ID: <20131223105429.CDCC9E0090@blue.fi.intel.com> (raw)
In-Reply-To: <20131223102524.GE11295@suse.de>

Mel Gorman wrote:
> On Fri, Dec 20, 2013 at 06:42:10PM +0100, Andrea Arcangeli wrote:
> > The reason for not doing this was that it felt slow to have that kind
> > of mangling in a fast path bad check. But maybe it's no problem to do
> > it. The above should also avoid the bug.
> > 
> 
> If this bug is related to mprotect then it should also have been fixed
> indirectly by commit 1667918b ("mm: numa: clear numa hinting information
> on mprotect") although for the wrong reasons. Applying cleanly requires
> 
>  mm: clear pmd_numa before invalidating
>  mm: numa: do not clear PMD during PTE update scan
>  mm: numa: do not clear PTE for pte_numa update
>  mm: numa: clear numa hinting information on mprotect
> 
> Is this bug reproducible in 3.13-rc5?

No. At least with my test case.

-- 
 Kirill A. Shutemov

--
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>

  reply	other threads:[~2013-12-23 10:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130223003232.4CDDB5A41B6@corp2gmr1-2.hot.corp.google.com>
     [not found] ` <52AA0613.2000908@oracle.com>
     [not found]   ` <CA+55aFw3_0_Et9bbfWgGLXEUaGQW1HE8j=oGBqFG_8j+h6jmvQ@mail.gmail.com>
     [not found]     ` <CA+55aFyRZW=Uy9w+bZR0vMOFNPqV-yW2Xs9N42qEwTQ3AY0fDw@mail.gmail.com>
     [not found]       ` <52AE271C.4040805@oracle.com>
2013-12-15 22:58         ` [patch 019/154] mm: make madvise(MADV_WILLNEED) support swap file prefetch Linus Torvalds
2013-12-16 12:47           ` Kirill A. Shutemov
2013-12-16 15:18             ` Sasha Levin
2013-12-16 20:52               ` Andrea Arcangeli
2013-12-17  0:18                 ` Sasha Levin
2013-12-17 12:44                   ` Kirill A. Shutemov
2013-12-17 14:09                     ` Sasha Levin
2013-12-20 13:10                 ` Kirill A. Shutemov
2013-12-20 13:31                   ` Kirill A. Shutemov
2013-12-20 13:36                   ` Kirill A. Shutemov
2013-12-20 17:42                     ` Andrea Arcangeli
2013-12-23 10:25                       ` Mel Gorman
2013-12-23 10:54                         ` Kirill A. Shutemov [this message]
2013-12-23 11:15                           ` 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=20131223105429.CDCC9E0090@blue.fi.intel.com \
    --to=kirill.shutemov@linux.intel.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=sasha.levin@oracle.com \
    --cc=shli@fusionio.com \
    --cc=shli@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.