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: Fri, 29 Apr 2022 12:03:17 -0400 [thread overview]
Message-ID: <20220429160317.GA71@qian> (raw)
In-Reply-To: <CA+G9fYveMF-NU-rvrsbaora2g2QWxrkF7AWViuDrJyN9mNScJg@mail.gmail.com>
On Fri, Apr 29, 2022 at 04:50:25PM +0530, Naresh Kamboju wrote:
> Following kernel warning notices on Linux next-20220427 till date next-20220429
> on qemu_arm64 and arm64 devices.
>
> While testing libhugetlbfs test suite and ltp mm and hugetlb.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
>
> Test log:
> ----------
> truncate_above_4GB (2M: 64): PASS
> brk_near_huge (2M: 64): brk_near_huge: malloc.c:2401: sysmalloc:
> Assertion `(old_top == initial_top (av) && old_size == 0) ||
> ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) &&
> ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
> [ 15.685019] audit: type=1701 audit(1651222753.772:25):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=454
> comm=\"brk_near_huge\"
> exe=\"/usr/lib/libhugetlbfs/tests/obj64/brk_near_huge\" sig=6 res=1
> [ 15.685629] ------------[ cut here ]------------
> [ 15.685631] WARNING: CPU: 2 PID: 454 at mm/page_alloc.c:5368
Naresh, I am having difficult to reproduce this reliablely. If you have
spare cycles, do you mind reverting those to see if you can still
reproduce? I can't seems to find other recent commits more suspicious
than that series.
37e73e3b0a9d drivers: virtio_mem: use pageblock size as the minimum virtio_mem size.
d2b9cd2acb2b mm: cma: use pageblock_order as the single alignment
7f125582227e mm: page_isolation: enable arbitrary range page isolation.
fb009b307b21 mm: make alloc_contig_range work at pageblock granularity
7c7e18d510f4 mm: page_isolation: check specified range for unmovable pages
6a242a94b883 mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c
$ git revert --no-edit e389355485b7..37e73e3b0a9d
next prev parent reply other threads:[~2022-04-29 16:03 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 [this message]
2022-04-29 22:11 ` Naresh Kamboju
2022-05-02 12:41 ` Qian Cai
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=20220429160317.GA71@qian \
--to=quic_qiancai@quicinc$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=chenwandun@huawei$(echo .)com \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=david@redhat$(echo .)com \
--cc=joao.m.martins@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=lkp@intel$(echo .)com \
--cc=mawupeng1@huawei$(echo .)com \
--cc=mgorman@techsingularity$(echo .)net \
--cc=minchan@kernel$(echo .)org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=neilb@suse$(echo .)de \
--cc=osalvador@suse$(echo .)de \
--cc=renzhengeek@gmail$(echo .)com \
--cc=richard.weiyang@gmail$(echo .)com \
--cc=rppt@linux$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=song@kernel$(echo .)org \
--cc=vbabka@suse$(echo .)cz \
--cc=ziy@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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