From: "Huang\, Ying" <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrei Vagin <avagin@openvz.org>,
Dan Williams <dan.j.williams@intel.com>,
Jerome Glisse <jglisse@redhat.com>,
Daniel Colascione <dancol@google.com>,
Zi Yan <zi.yan@cs.rutgers.edu>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH -mm] mm, pagemap: Fix swap offset value for PMD migration entry
Date: Tue, 10 Apr 2018 08:57:19 +0800 [thread overview]
Message-ID: <87in8znaj4.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20180409174753.4b959a5b3ff732b8f96f5a14@linux-foundation.org> (Andrew Morton's message of "Mon, 9 Apr 2018 17:47:53 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Sun, 8 Apr 2018 11:37:37 +0800 "Huang, Ying" <ying.huang@intel.com> wrote:
>
>> From: Huang Ying <ying.huang@intel.com>
>>
>> The swap offset reported by /proc/<pid>/pagemap may be not correct for
>> PMD migration entry. If addr passed into pagemap_range() isn't
>
> pagemap_pmd_range(), yes?
Yes. Sorry for typo.
>> aligned with PMD start address,
>
> How can this situation come about?
After open /proc/<pid>/pagemap, if user seeks to a page whose address
doesn't aligned with PMD start address. I have verified this with a
simple test program.
>> the swap offset reported doesn't
>> reflect this. And in the loop to report information of each sub-page,
>> the swap offset isn't increased accordingly as that for PFN.
>>
>> BTW: migration swap entries have PFN information, do we need to
>> restrict whether to show them?
>
> For what reason? Address obfuscation?
This is an existing feature for PFN report of /proc/<pid>/pagemap,
reason is in following commit log. I am wondering whether that is
necessary for migration swap entries too.
ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
AuthorDate: Mon Mar 9 23:11:12 2015 +0200
Commit: Linus Torvalds <torvalds@linux-foundation.org>
CommitDate: Tue Mar 17 09:31:30 2015 -0700
pagemap: do not leak physical addresses to non-privileged userspace
As pointed by recent post[1] on exploiting DRAM physical imperfection,
/proc/PID/pagemap exposes sensitive information which can be used to do
attacks.
This disallows anybody without CAP_SYS_ADMIN to read the pagemap.
[1] http://googleprojectzero.blogspot.com/2015/03/exploiting-dram-rowhammer-bug-to-gain.html
[ Eventually we might want to do anything more finegrained, but for now
this is the simple model. - Linus ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
Acked-by: Andy Lutomirski <luto@amacapital.net>
Cc: Pavel Emelyanov <xemul@parallels.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Seaborn <mseaborn@chromium.org>
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrei Vagin <avagin@openvz.org>,
Dan Williams <dan.j.williams@intel.com>,
Jerome Glisse <jglisse@redhat.com>,
Daniel Colascione <dancol@google.com>,
Zi Yan <zi.yan@cs.rutgers.edu>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH -mm] mm, pagemap: Fix swap offset value for PMD migration entry
Date: Tue, 10 Apr 2018 08:57:19 +0800 [thread overview]
Message-ID: <87in8znaj4.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20180409174753.4b959a5b3ff732b8f96f5a14@linux-foundation.org> (Andrew Morton's message of "Mon, 9 Apr 2018 17:47:53 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Sun, 8 Apr 2018 11:37:37 +0800 "Huang, Ying" <ying.huang@intel.com> wrote:
>
>> From: Huang Ying <ying.huang@intel.com>
>>
>> The swap offset reported by /proc/<pid>/pagemap may be not correct for
>> PMD migration entry. If addr passed into pagemap_range() isn't
>
> pagemap_pmd_range(), yes?
Yes. Sorry for typo.
>> aligned with PMD start address,
>
> How can this situation come about?
After open /proc/<pid>/pagemap, if user seeks to a page whose address
doesn't aligned with PMD start address. I have verified this with a
simple test program.
>> the swap offset reported doesn't
>> reflect this. And in the loop to report information of each sub-page,
>> the swap offset isn't increased accordingly as that for PFN.
>>
>> BTW: migration swap entries have PFN information, do we need to
>> restrict whether to show them?
>
> For what reason? Address obfuscation?
This is an existing feature for PFN report of /proc/<pid>/pagemap,
reason is in following commit log. I am wondering whether that is
necessary for migration swap entries too.
ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
AuthorDate: Mon Mar 9 23:11:12 2015 +0200
Commit: Linus Torvalds <torvalds@linux-foundation.org>
CommitDate: Tue Mar 17 09:31:30 2015 -0700
pagemap: do not leak physical addresses to non-privileged userspace
As pointed by recent post[1] on exploiting DRAM physical imperfection,
/proc/PID/pagemap exposes sensitive information which can be used to do
attacks.
This disallows anybody without CAP_SYS_ADMIN to read the pagemap.
[1] http://googleprojectzero.blogspot.com/2015/03/exploiting-dram-rowhammer-bug-to-gain.html
[ Eventually we might want to do anything more finegrained, but for now
this is the simple model. - Linus ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
Acked-by: Andy Lutomirski <luto@amacapital.net>
Cc: Pavel Emelyanov <xemul@parallels.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Seaborn <mseaborn@chromium.org>
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2018-04-10 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 3:37 [PATCH -mm] mm, pagemap: Fix swap offset value for PMD migration entry Huang, Ying
2018-04-10 0:47 ` Andrew Morton
2018-04-10 0:57 ` Huang, Ying [this message]
2018-04-10 0:57 ` Huang, Ying
2018-04-10 11:12 ` Kirill A. Shutemov
2018-04-11 0:56 ` Huang, Ying
2018-04-11 0:56 ` Huang, Ying
2018-04-10 1:28 ` Huang, Ying
2018-04-10 1:28 ` 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=87in8znaj4.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=dan.j.williams@intel.com \
--cc=dancol@google.com \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=zi.yan@cs.rutgers.edu \
/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.