From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@suse.com>,
Heiko Carstens <hca@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [RFC] linux-next panic in hugepage_subpool_put_pages()
Date: Tue, 23 Feb 2021 18:08:20 -0800 [thread overview]
Message-ID: <20210223180820.ee39f1544f2630d0eecf3a57@linux-foundation.org> (raw)
In-Reply-To: <44d50df7-9940-6a37-179f-ee2aa6cf34b9@oracle.com>
On Tue, 23 Feb 2021 17:29:48 -0800 Mike Kravetz <mike.kravetz@oracle.com> wrote:
> >> I will do a bit more verification and put together a patch (it should
> >> be simple).
> >
> > There's also Michel's documentation request:
> > https://lkml.kernel.org/r/20210127102645.GH827@dhcp22.suse.cz
> >
>
> Thanks Andrew, I forgot about that.
>
> It looks like the patch which added synchronization documentation requested
> by Michal may not have be picked up.
> https://lore.kernel.org/linux-mm/9183032f-3d77-d9e3-9cc8-fbaf3e892022@oracle.com/
OK, I grabbed that.
> If you still need to add that patch, I could redo and add the page[1]->private
> documentation request mentioned here. Just let me know what is the easiest for
> you.
Please send along an additional patch?
next prev parent reply other threads:[~2021-02-24 2:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 14:57 [RFC] linux-next panic in hugepage_subpool_put_pages() Gerald Schaefer
2021-02-23 16:45 ` Gerald Schaefer
2021-02-23 18:06 ` Mike Kravetz
2021-02-23 23:58 ` Andrew Morton
2021-02-24 1:29 ` Mike Kravetz
2021-02-24 2:08 ` Andrew Morton [this message]
2021-02-24 4:04 ` [PATCH] hugetlb: document the new location of page subpool pointer Mike Kravetz
2021-02-24 8:20 ` Oscar Salvador
2021-02-24 8:48 ` [External] " Muchun Song
2021-02-24 10:06 ` 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=20210223180820.ee39f1544f2630d0eecf3a57@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=svens@linux.ibm.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).