linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Will Deacon <will.deacon@arm.com>
Cc: kirill.shutemov@linux.intel.com, oleg@redhat.com, hpa@zytor.com,
	luto@amacapital.net, dave.hansen@linux.intel.com, mingo@elte.hu,
	minchan@kernel.org, tglx@linutronix.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: RE: LTP regressions due to 6dc296e7df4c ("mm: make sure all file VMAs have ->vm_ops set")
Date: Mon, 14 Sep 2015 14:57:59 +0300 (EEST)	[thread overview]
Message-ID: <20150914115800.06242CE@black.fi.intel.com> (raw)
In-Reply-To: <20150914105346.GB23878@arm.com>

Will Deacon wrote:
> Hi Kirill,
> 
> Your patch 6dc296e7df4c ("mm: make sure all file VMAs have ->vm_ops set")
> causes some mmap regressions in LTP, which appears to use a MAP_PRIVATE
> mmap of /dev/zero as a way to get anonymous pages in some of its tests
> (specifically mmap10 [1]).
> 
> Dead simple reproducer below. Is this change in behaviour intentional?

Ouch. Of couse it's a bug.

Fix is below. I don't really like it, but I cannot find any better
solution.

  reply	other threads:[~2015-09-14 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 10:53 LTP regressions due to 6dc296e7df4c ("mm: make sure all file VMAs have ->vm_ops set") Will Deacon
2015-09-14 11:57 ` Kirill A. Shutemov [this message]
2015-09-14 13:22   ` Will Deacon
2015-09-14 17:05   ` Oleg Nesterov
2015-09-14 17:46     ` Oleg Nesterov
2015-09-14 18:20     ` Kirill A. Shutemov
2015-09-15 12:12       ` Oleg Nesterov
2015-09-15 13:42         ` Kirill A. Shutemov
2015-09-15 15:13           ` Oleg Nesterov
2015-09-16 21:28           ` Andrew Morton
2015-09-17 15:37             ` 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=20150914115800.06242CE@black.fi.intel.com \
    --to=kirill.shutemov@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=minchan@kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.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).