From: Qian Cai <quic_qiancai@quicinc.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>,
<lkft-triage@lists.linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>, "Zi Yan" <ziy@nvidia.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"David Hildenbrand" <david@redhat.com>,
Eric Ren <renzhengeek@gmail.com>,
"kernel test robot" <lkp@intel.com>,
Mel Gorman <mgorman@techsingularity.net>,
"Mike Rapoport" <rppt@linux.ibm.com>,
Minchan Kim <minchan@kernel.org>,
"Oscar Salvador" <osalvador@suse.de>,
Vlastimil Babka <vbabka@suse.cz>,
Chen Wandun <chenwandun@huawei.com>, NeilBrown <neilb@suse.de>,
<joao.m.martins@oracle.com>, <mawupeng1@huawei.com>,
Wei Yang <richard.weiyang@gmail.com>, Song Liu <song@kernel.org>
Subject: Re: [next] mm: libhugetlbfs: WARNING: at mm/page_alloc.c:5368 __alloc_pages
Date: Mon, 2 May 2022 08:41:46 -0400 [thread overview]
Message-ID: <20220502124146.GA71@qian> (raw)
In-Reply-To: <CA+G9fYui9OuyFbg7SV8D_4ueC_Jc=71ybbhBeif0bczo957Hqg@mail.gmail.com>
On Sat, Apr 30, 2022 at 03:41:41AM +0530, Naresh Kamboju wrote:
> The reported kernel warning was not solved by reverted above patches.
Thanks for the confirmation. Then, I can't think of any other good
candidates at the moment apart from doing brutal-force bisecting.
next prev parent reply other threads:[~2022-05-02 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 11:20 [next] mm: libhugetlbfs: WARNING: at mm/page_alloc.c:5368 __alloc_pages Naresh Kamboju
2022-04-29 16:03 ` Qian Cai
2022-04-29 22:11 ` Naresh Kamboju
2022-05-02 12:41 ` Qian Cai [this message]
2022-05-03 22:26 ` Qian Cai
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=20220502124146.GA71@qian \
--to=quic_qiancai@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=chenwandun@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkp@intel.com \
--cc=mawupeng1@huawei.com \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=neilb@suse.de \
--cc=osalvador@suse.de \
--cc=renzhengeek@gmail.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=song@kernel.org \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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.