From: "Zhang, Wei" <wzam@amazon.com>
To: Jason Gunthorpe <jgg@ziepe.ca>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Xu <peterx@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pressman, Gal" <galpress@amazon.com>,
Matthew Wilcox <willy@infradead.org>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Gibson <david@gibson.dropbear.id.au>,
Jann Horn <jannh@google.com>, Kirill Tkhai <ktkhai@virtuozzo.com>,
"Kirill Shutemov" <kirill@shutemov.name>,
Miaohe Lin <linmiaohe@huawei.com>,
"Andrea Arcangeli" <aarcange@redhat.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v5 0/5] mm/hugetlb: Early cow on fork, and a few cleanups
Date: Tue, 2 Mar 2021 00:59:40 +0000 [thread overview]
Message-ID: <AE355B8D-8496-4CDF-9BC0-A8D6DE0F9C34@amazon.com> (raw)
In-Reply-To: <20210302003035.GE444867@ziepe.ca>
Yes, such user includes libfabric (https://ofiwg.github.io/libfabric/) . which uses hugetlb pages.
On 3/1/21, 4:30 PM, "Jason Gunthorpe" <jgg@ziepe.ca> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Mon, Mar 01, 2021 at 04:28:46PM -0800, Andrew Morton wrote:
> On Mon, 1 Mar 2021 09:11:51 -0500 Peter Xu <peterx@redhat.com> wrote:
>
> > On Wed, Feb 17, 2021 at 06:35:42PM -0500, Peter Xu wrote:
> > > v5:
> > > - patch 4: change "int cow" into "bool cow"
> > > - collect r-bs for Jason
> >
> > Andrew,
> >
> > I just noticed 5.12-rc1 has released; is this series still possible to make it
> > for 5.12, or needs to wait for 5.13?
> >
>
> It has taken a while to settle down. What is the case for
> fast-tracking it into 5.12?
IIRC hugetlb users and fork and DMA will get the unexpected VA
corruption that triggered all this work.
Jason
next prev parent reply other threads:[~2021-03-02 0:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 23:35 [PATCH v5 0/5] mm/hugetlb: Early cow on fork, and a few cleanups Peter Xu
2021-02-17 23:35 ` [PATCH v5 1/5] hugetlb: Dedup the code to add a new file_region Peter Xu
2021-02-17 23:35 ` [PATCH v5 2/5] hugetlg: Break earlier in add_reservation_in_range() when we can Peter Xu
2021-02-17 23:35 ` [PATCH v5 3/5] mm: Introduce page_needs_cow_for_dma() for deciding whether cow Peter Xu
2021-02-17 23:35 ` [PATCH v5 4/5] mm: Use is_cow_mapping() across tree where proper Peter Xu
2021-02-17 23:35 ` [PATCH v5 5/5] hugetlb: Do early cow when page pinned on src mm Peter Xu
2021-03-01 14:11 ` [PATCH v5 0/5] mm/hugetlb: Early cow on fork, and a few cleanups Peter Xu
2021-03-02 0:28 ` Andrew Morton
2021-03-02 0:30 ` Jason Gunthorpe
2021-03-02 0:59 ` Zhang, Wei [this message]
2021-03-03 1:46 ` Peter Xu
2021-03-03 2:45 ` Linus Torvalds
2021-03-04 17:10 ` Jason Gunthorpe
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=AE355B8D-8496-4CDF-9BC0-A8D6DE0F9C34@amazon.com \
--to=wzam@amazon.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@gibson.dropbear.id.au \
--cc=galpress@amazon.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=kirill@shutemov.name \
--cc=ktkhai@virtuozzo.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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).