From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"broonie@kernel.org" <broonie@kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"mhocko@suse.cz" <mhocko@suse.cz>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Subject: Re: mmotm 2021-05-12-21-46 uploaded (mm/memory_failure.c)
Date: Thu, 13 May 2021 05:36:44 +0000 [thread overview]
Message-ID: <20210513053643.GA661371@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <91fd4441-b84b-ceb0-8d4c-c62e631711fc@infradead.org>
On Wed, May 12, 2021 at 10:28:29PM -0700, Randy Dunlap wrote:
> On 5/12/21 9:47 PM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2021-05-12-21-46 has been uploaded to
> >
> > https://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for mm-of-the-moment:
> >
> > https://www.ozlabs.org/~akpm/mmotm/
> >
> > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > more than once a week.
> >
> > You will need quilt to apply these patches to the latest Linus release (5.x
> > or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> > https://ozlabs.org/~akpm/mmotm/series
> >
> > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> > followed by the base kernel version against which this patch series is to
> > be applied.
> >
> > This tree is partially included in linux-next. To see which patches are
> > included in linux-next, consult the `series' file. Only the patches
> > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > linux-next.
>
> on x86_64:
> # CONFIG_HUGETLBFS is not set
>
> ../mm/memory-failure.c: In function ‘__get_hwpoison_page’:
> ../mm/memory-failure.c:962:15: error: ‘hugetlb_lock’ undeclared (first use in this function); did you mean ‘huge_pte_lock’?
> spin_lock(&hugetlb_lock);
> ^~~~~~~~~~~~
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
Thanks, we need "#ifdef CONFIG_HUGETLB_PAGE" for the added code.
And this patch is still under discussion and needs to be updated.
So Andrew, could you drop the following patches from linux-mm?
mmhwpoison-make-get_hwpoison_page-call-get_any_page.patch added to -mm tree
mmhwpoison-fix-race-with-compound-page-allocation.patch added to -mm tree
- Naoya
next prev parent reply other threads:[~2021-05-13 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 4:47 mmotm 2021-05-12-21-46 uploaded akpm
2021-05-13 5:28 ` mmotm 2021-05-12-21-46 uploaded (mm/memory_failure.c) Randy Dunlap
2021-05-13 5:36 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2021-05-13 15:54 ` mmotm 2021-05-12-21-46 uploaded (arch/x86/mm/pgtable.c) Randy Dunlap
2021-05-13 17:09 ` Christophe Leroy
2021-05-13 20:47 ` Andrew Morton
2021-05-13 21:08 ` Randy Dunlap
2021-05-14 9:45 ` Naresh Kamboju
2021-05-14 21:40 ` Andrew Morton
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=20210513053643.GA661371@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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