linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <zi.yan@cs.rutgers.edu>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	"Michal Hocko" <mhocko@suse.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	"David Rientjes" <rientjes@google.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Hugh Dickins" <hughd@google.com>,
	"J�r�me Glisse" <jglisse@redhat.com>,
	"Daniel Colascione" <dancol@google.com>,
	"Naoya Horiguchi" <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH -mm] mm, pagemap: Fix soft dirty marking for PMD migration entry
Date: Tue, 17 Oct 2017 08:33:05 -0400	[thread overview]
Message-ID: <59E5F881.20105@cs.rutgers.edu> (raw)
In-Reply-To: <874lqy7yks.fsf@yhuang-dev.intel.com>

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



Huang, Ying wrote:
> "Kirill A. Shutemov" <kirill@shutemov.name> writes:
> 
>> On Tue, Oct 17, 2017 at 04:18:18PM +0800, Huang, Ying wrote:
>>> From: Huang Ying <ying.huang@intel.com>
>>>
>>> Now, when the page table is walked in the implementation of
>>> /proc/<pid>/pagemap, pmd_soft_dirty() is used for both the PMD huge
>>> page map and the PMD migration entries.  That is wrong,
>>> pmd_swp_soft_dirty() should be used for the PMD migration entries
>>> instead because the different page table entry flag is used.
>>>
>>> Cc: Michal Hocko <mhocko@suse.com>
>>> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>>> Cc: David Rientjes <rientjes@google.com>
>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>> Cc: Hugh Dickins <hughd@google.com>
>>> Cc: "J.r.me Glisse" <jglisse@redhat.com>
>>> Cc: Daniel Colascione <dancol@google.com>
>>> Cc: Zi Yan <zi.yan@cs.rutgers.edu>
>>> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>>> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
>> What is effect of the misbehaviour? pagemap reports garbage?
> 
> Yes.  pagemap may report incorrect soft dirty information for PMD
> migration entries.

Thanks for fixing it.

> 
>> Shoudn't it be in stable@? And maybe add Fixes: <sha1>.
> 
> Yes.  Will do that in the next version.

PMD migration is merged in 4.14, which is not final yet. Do we need to
split the patch, so that first hunk(for present PMD entries) goes into
stable and second hunk(for PMD migration entries) goes into 4.14?

-- 
Best Regards,
Yan Zi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 537 bytes --]

  reply	other threads:[~2017-10-17 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  8:18 [PATCH -mm] mm, pagemap: Fix soft dirty marking for PMD migration entry Huang, Ying
2017-10-17  9:47 ` Anshuman Khandual
2017-10-17 11:21 ` Kirill A. Shutemov
2017-10-17 12:23   ` Huang, Ying
2017-10-17 12:33     ` Zi Yan [this message]
2017-10-17 13:55       ` Huang, Ying

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=59E5F881.20105@cs.rutgers.edu \
    --to=zi.yan@cs.rutgers.edu \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dancol@google.com \
    --cc=hughd@google.com \
    --cc=jglisse@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rientjes@google.com \
    --cc=ying.huang@intel.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).