From: Qian Cai <quic_qiancai@quicinc.com>
To: Zi Yan <ziy@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Eric Ren <renzhengeek@gmail.com>, Mike Rapoport <rppt@kernel.org>,
"Oscar Salvador" <osalvador@suse.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment.
Date: Thu, 28 Apr 2022 12:19:11 -0400 [thread overview]
Message-ID: <20220428161911.GB182@qian> (raw)
In-Reply-To: <0E75B247-8150-48A3-83AE-56C586030006@nvidia.com>
On Thu, Apr 28, 2022 at 08:39:06AM -0400, Zi Yan wrote:
> How about the one attached? I can apply it to next-20220428. Let me know
> if you are using a different branch. Thanks.
The original endless loop is gone, but running some syscall fuzzer
afterwards for a while would trigger the warning here. I have yet to
figure out if this is related to this series.
/*
* There are several places where we assume that the order value is sane
* so bail out early if the request is out of bound.
*/
if (unlikely(order >= MAX_ORDER)) {
WARN_ON_ONCE(!(gfp & __GFP_NOWARN));
return NULL;
}
WARNING: CPU: 26 PID: 172874 at mm/page_alloc.c:5368 __alloc_pages
CPU: 26 PID: 172874 Comm: trinity-main Not tainted 5.18.0-rc4-next-20220428-dirty #67
pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
tpidr_el2 : ffff28cf80a61000
pc : __alloc_pages
lr : alloc_pages
sp : ffff8000597b70f0
x29: ffff8000597b70f0 x28: ffff0801e68d34c0 x27: 0000000000000000
x26: 1ffff0000b2f6ea2 x25: ffff8000597b7510 x24: 0000000000000dc0
x23: ffff28cf80a61000 x22: 000000000000000e x21: 1ffff0000b2f6e28
x20: 0000000000040dc0 x19: ffffdf670d4a6fe0 x18: ffffdf66fa017d1c
x17: ffffdf66f42f8348 x16: 1fffe1003cd1a7b3 x15: 000000000000001a
x14: 1fffe1003cd1a7a6 x13: 0000000000000004 x12: ffff70000b2f6e05
x11: 1ffff0000b2f6e04 x10: 00000000f204f1f1 x9 : 000000000000f204
x8 : dfff800000000000 x7 : 00000000f3000000 x6 : 00000000f3f3f3f3
x5 : ffff70000b2f6e28 x4 : ffff0801e68d34c0 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000040dc0
Call trace:
__alloc_pages
alloc_pages
kmalloc_order
kmalloc_order_trace
__kmalloc
__regset_get
regset_get_alloc
fill_thread_core_info
fill_note_info
elf_core_dump
do_coredump
get_signal
do_signal
do_notify_resume
el0_svc
el0t_64_sync_handler
el0t_64_sync
irq event stamp: 3614
hardirqs last enabled at (3613): _raw_spin_unlock_irqrestore
hardirqs last disabled at (3614): el1_dbg
softirqs last enabled at (2988): fpsimd_preserve_current_state
softirqs last disabled at (2986): fpsimd_preserve_current_state
next prev parent reply other threads:[~2022-04-28 16:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:31 [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 1/6] mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c Zi Yan
2022-04-25 14:31 ` [PATCH v11 2/6] mm: page_isolation: check specified range for unmovable pages Zi Yan
2022-04-25 14:31 ` [PATCH v11 3/6] mm: make alloc_contig_range work at pageblock granularity Zi Yan
2022-04-29 13:54 ` Zi Yan
2022-05-24 19:00 ` Zi Yan
2022-05-25 17:41 ` Doug Berger
2022-05-25 17:53 ` Zi Yan
2022-05-25 21:03 ` Doug Berger
2022-05-25 21:11 ` Zi Yan
2022-05-26 17:34 ` Zi Yan
2022-05-26 19:46 ` Doug Berger
2022-04-25 14:31 ` [PATCH v11 4/6] mm: page_isolation: enable arbitrary range page isolation Zi Yan
2022-05-24 19:02 ` Zi Yan
2022-04-25 14:31 ` [PATCH v11 5/6] mm: cma: use pageblock_order as the single alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 6/6] drivers: virtio_mem: use pageblock size as the minimum virtio_mem size Zi Yan
2022-04-26 20:18 ` [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Qian Cai
2022-04-26 20:26 ` Zi Yan
2022-04-26 21:08 ` Qian Cai
2022-04-26 21:38 ` Zi Yan
2022-04-27 12:41 ` Qian Cai
2022-04-27 13:10 ` Qian Cai
2022-04-27 13:27 ` Qian Cai
2022-04-27 13:30 ` Zi Yan
2022-04-27 21:04 ` Zi Yan
2022-04-28 12:33 ` Qian Cai
2022-04-28 12:39 ` Zi Yan
2022-04-28 16:19 ` Qian Cai [this message]
2022-04-29 13:38 ` Zi Yan
2022-05-19 20:57 ` Qian Cai
2022-05-19 21:35 ` Zi Yan
2022-05-19 23:24 ` Zi Yan
2022-05-20 11:30 ` Qian Cai
2022-05-20 13:43 ` Zi Yan
2022-05-20 14:13 ` Zi Yan
2022-05-20 19:41 ` Qian Cai
2022-05-20 21:56 ` Zi Yan
2022-05-20 23:41 ` Qian Cai
2022-05-22 16:54 ` Zi Yan
2022-05-22 19:33 ` Zi Yan
2022-05-24 16:59 ` Qian Cai
2022-05-10 1:03 ` Andrew Morton
2022-05-10 1:03 ` Andrew Morton
2022-05-10 1:07 ` Zi Yan
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=20220428161911.GB182@qian \
--to=quic_qiancai@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=renzhengeek@gmail.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=virtualization@lists.linux-foundation.org \
--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.