linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Jann Horn <jannh@google.com>
Cc: security@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	Yang Shi <shy828301@gmail.com>, Peter Xu <peterx@redhat.com>,
	John Hubbard <jhubbard@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 3/3] mm/khugepaged: Invoke MMU notifiers in shmem/file collapse paths
Date: Mon, 28 Nov 2022 19:06:01 +0100	[thread overview]
Message-ID: <54f43e4d-5124-b2c8-c6d4-ce0bf4547eaf@redhat.com> (raw)
In-Reply-To: <CAG48ez23WvRRX6LKgCe+sJMYWBKVa+U1fg7G1o0nOobHCEQBGg@mail.gmail.com>

On 28.11.22 18:57, Jann Horn wrote:
> On Mon, Nov 28, 2022 at 6:37 PM David Hildenbrand <david@redhat.com> wrote:
>>
>> On 25.11.22 22:37, Jann Horn wrote:
>>> Any codepath that zaps page table entries must invoke MMU notifiers to
>>> ensure that secondary MMUs (like KVM) don't keep accessing pages which
>>> aren't mapped anymore. Secondary MMUs don't hold their own references to
>>> pages that are mirrored over, so failing to notify them can lead to page
>>> use-after-free.
>>>
>>> I'm marking this as addressing an issue introduced in commit f3f0e1d2150b
>>> ("khugepaged: add support of collapse for tmpfs/shmem pages"), but most of
>>> the security impact of this only came in commit 27e1f8273113 ("khugepaged:
>>> enable collapse pmd for pte-mapped THP"), which actually omitted flushes
>>> for the removal of present PTEs, not just for the removal of empty page
>>> tables.
>>>
>>> Cc: stable@kernel.org
>>> Fixes: f3f0e1d2150b ("khugepaged: add support of collapse for tmpfs/shmem pages")
>>
>> I'm curious, do you have a working reproducer for this?
> 
> You're on the CC list of my bug report to security@kernel.org
> with title "khugepaged races with rmap-based zap, races with GUP-fast,
> and fails to call MMU notifiers". That has an attached reproducer
> thp_ro_no_notify_kvm.c that is able to read PAGE_POISON out of freed
> file THP pages through KVM.
> 

Ah, the mail from early October, thanks (drowning in mail).

You're amazingly skilled at writing reproducers.

-- 
Thanks,

David / dhildenb


  reply	other threads:[~2022-11-28 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 21:37 [PATCH v3 1/3] mm/khugepaged: Take the right locks for page table retraction Jann Horn
2022-11-25 21:37 ` [PATCH v3 2/3] mm/khugepaged: Fix GUP-fast interaction by sending IPI Jann Horn
2022-11-28 13:46   ` David Hildenbrand
2022-11-28 16:58     ` Jann Horn
2022-11-28 17:00       ` David Hildenbrand
2022-11-25 21:37 ` [PATCH v3 3/3] mm/khugepaged: Invoke MMU notifiers in shmem/file collapse paths Jann Horn
2022-11-28 17:37   ` David Hildenbrand
2022-11-28 17:57     ` Jann Horn
2022-11-28 18:06       ` David Hildenbrand [this message]
2022-11-28 13:52 ` [PATCH v3 1/3] mm/khugepaged: Take the right locks for page table retraction David Hildenbrand
2022-11-28 17:28   ` Jann Horn
2022-11-28 17:34     ` David Hildenbrand

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=54f43e4d-5124-b2c8-c6d4-ce0bf4547eaf@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=security@kernel.org \
    --cc=shy828301@gmail.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).