From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Xu <peterx@redhat.com>, Jerome Glisse <jglisse@redhat.com>,
Shaohua Li <shli@fb.com>
Subject: Re: [PATCH v1] mm/userfaultfd: propagate uffd-wp bit when PTE-mapping the huge zeropage
Date: Fri, 3 Mar 2023 10:12:46 +0100 [thread overview]
Message-ID: <22681eea-fac6-9a51-df43-b5613b75bdaa@redhat.com> (raw)
In-Reply-To: <20230302175734.7be9da18e4724720a12a4b40@linux-foundation.org>
>> Fixes: e06f1e1dd499 ("userfaultfd: wp: enabled write protection in userfaultfd API")
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>
>> Cc: Andrea Arcangeli <aarcange@redhat.com>
>> Cc: Peter Xu <peterx@redhat.com>
>> Cc: Jerome Glisse <jglisse@redhat.com>
>> Cc: Shaohua Li <shli@fb.com>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>
> Do you agree that a -stable backport is appropriate?
Yes, actually I wanted to include the tag but somehow I dropped it. Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-03-03 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 17:54 [PATCH v1] mm/userfaultfd: propagate uffd-wp bit when PTE-mapping the huge zeropage David Hildenbrand
2023-03-02 22:29 ` Peter Xu
2023-03-03 9:12 ` David Hildenbrand
2023-03-03 14:32 ` Peter Xu
2023-03-03 1:57 ` Andrew Morton
2023-03-03 9:12 ` David Hildenbrand [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 1:11 kernel test robot
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=22681eea-fac6-9a51-df43-b5613b75bdaa@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=shli@fb.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 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.