From: Alexander Gordeev <agordeev@linux•ibm.com>
To: Andrew Morton <akpm@linux-foundation•org>,
Gerald Schaefer <gerald.schaefer@linux•ibm.com>
Cc: Nico Pache <npache@redhat•com>,
linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-mm@kvack•org, linux-trace-kernel@vger•kernel.org,
aarcange@redhat•com, anshuman.khandual@arm•com,
apopple@nvidia•com, baohua@kernel•org,
baolin.wang@linux•alibaba.com, byungchul@sk•com,
catalin.marinas@arm•com, cl@gentwo•org, corbet@lwn•net,
dave.hansen@linux•intel.com, david@kernel•org, dev.jain@arm•com,
gourry@gourry•net, hannes@cmpxchg•org, hughd@google•com,
jack@suse•cz, jackmanb@google•com, jannh@google•com,
jglisse@google•com, joshua.hahnjy@gmail•com, kas@kernel•org,
lance.yang@linux•dev, liam@infradead•org, ljs@kernel•org,
mathieu.desnoyers@efficios•com, matthew.brost@intel•com,
mhiramat@kernel•org, mhocko@suse•com, peterx@redhat•com,
pfalcato@suse•de, rakie.kim@sk•com, raquini@redhat•com,
rdunlap@infradead•org, richard.weiyang@gmail•com,
rientjes@google•com, rostedt@goodmis•org, rppt@kernel•org,
ryan.roberts@arm•com, shivankg@amd•com, sunnanyong@huawei•com,
surenb@google•com, thomas.hellstrom@linux•intel.com,
tiwai@suse•de, usamaarif642@gmail•com, vbabka@suse•cz,
vishal.moola@gmail•com, wangkefeng.wang@huawei•com,
will@kernel•org, willy@infradead•org,
yang@os•amperecomputing.com, ying.huang@linux•alibaba.com,
ziy@nvidia•com, zokeefe@google•com, linux-s390@vger•kernel.org,
linux-next@vger•kernel.org
Subject: Re: [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP collapse support
Date: Mon, 1 Jun 2026 17:58:08 +0200 [thread overview]
Message-ID: <20260601155808.2755103A59-agordeev@linux.ibm.com> (raw)
In-Reply-To: <20260522134724.f4f11941a85ef18b307d16ae@linux-foundation.org>
On Fri, May 22, 2026 at 01:47:24PM -0700, Andrew Morton wrote:
Hi Andrew et al,
> On Fri, 22 May 2026 08:59:55 -0600 Nico Pache <npache@redhat•com> wrote:
>
> > The following series provides khugepaged with the capability to collapse
> > anonymous memory regions to mTHPs.
>
> Thanks, I've update mm.git's mm-unstable branch to this version.
>
> It sounds like I might be dropping it soon, haven't started looking at
> that yet. But let's at least eyeball the latest version at this time.
>
> Sashiko was able to apply this, so the base-it-on-hotfixes thing worked
> well, thanks. The AI checking made a few allegations:
This series appears to cause hangs on s390 in linux-next.
The issue is not easily reproducible, so it is not yet confirmed.
Any ideas for a reliable reproducer that exercises the code path below?
[ 2749.385719] sysrq: Show Blocked State
[ 2749.385730] task:khugepaged state:D stack:0 pid:209 tgid:209 ppid:2 task_flags:0x200040 flags:0x00000000
[ 2749.385735] Call Trace:
[ 2749.385736] [<0000017f63c8b226>] __schedule+0x316/0x890
[ 2749.385740] [<0000017f63c8b7dc>] schedule+0x3c/0xc0
[ 2749.385743] [<0000017f63c8b888>] schedule_preempt_disabled+0x28/0x40
[ 2749.385746] [<0000017f63c902ea>] rwsem_down_write_slowpath+0x2fa/0x8b0
[ 2749.385749] [<0000017f63c90910>] down_write+0x70/0x80
[ 2749.385752] [<0000017f6313407a>] collapse_huge_page+0x2ea/0x9e0
[ 2749.385755] [<0000017f6313491e>] mthp_collapse+0x1ae/0x1f0
[ 2749.385757] [<0000017f63134fda>] collapse_scan_pmd+0x67a/0x8f0
[ 2749.385760] [<0000017f6313751a>] collapse_single_pmd+0x15a/0x260
[ 2749.385762] [<0000017f6313792c>] collapse_scan_mm_slot.constprop.0+0x30c/0x470
[ 2749.385765] [<0000017f63137cb6>] khugepaged+0x226/0x240
[ 2749.385768] [<0000017f62db3128>] kthread+0x148/0x170
[ 2749.385770] [<0000017f62d2c238>] __ret_from_fork+0x48/0x220
[ 2749.385772] [<0000017f63c95d0a>] ret_from_fork+0xa/0x30
Thanks!
next parent reply other threads:[~2026-06-01 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260522150009.121603-1-npache@redhat.com>
[not found] ` <20260522134724.f4f11941a85ef18b307d16ae@linux-foundation.org>
2026-06-01 15:58 ` Alexander Gordeev [this message]
2026-06-01 17:05 ` [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP collapse support Nico Pache
2026-06-01 17:08 ` Lorenzo Stoakes
2026-06-02 1:53 ` Lance Yang
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=20260601155808.2755103A59-agordeev@linux.ibm.com \
--to=agordeev@linux$(echo .)ibm.com \
--cc=aarcange@redhat$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=anshuman.khandual@arm$(echo .)com \
--cc=apopple@nvidia$(echo .)com \
--cc=baohua@kernel$(echo .)org \
--cc=baolin.wang@linux$(echo .)alibaba.com \
--cc=byungchul@sk$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=cl@gentwo$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=david@kernel$(echo .)org \
--cc=dev.jain@arm$(echo .)com \
--cc=gerald.schaefer@linux$(echo .)ibm.com \
--cc=gourry@gourry$(echo .)net \
--cc=hannes@cmpxchg$(echo .)org \
--cc=hughd@google$(echo .)com \
--cc=jack@suse$(echo .)cz \
--cc=jackmanb@google$(echo .)com \
--cc=jannh@google$(echo .)com \
--cc=jglisse@google$(echo .)com \
--cc=joshua.hahnjy@gmail$(echo .)com \
--cc=kas@kernel$(echo .)org \
--cc=lance.yang@linux$(echo .)dev \
--cc=liam@infradead$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-trace-kernel@vger$(echo .)kernel.org \
--cc=ljs@kernel$(echo .)org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=matthew.brost@intel$(echo .)com \
--cc=mhiramat@kernel$(echo .)org \
--cc=mhocko@suse$(echo .)com \
--cc=npache@redhat$(echo .)com \
--cc=peterx@redhat$(echo .)com \
--cc=pfalcato@suse$(echo .)de \
--cc=rakie.kim@sk$(echo .)com \
--cc=raquini@redhat$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=richard.weiyang@gmail$(echo .)com \
--cc=rientjes@google$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=rppt@kernel$(echo .)org \
--cc=ryan.roberts@arm$(echo .)com \
--cc=shivankg@amd$(echo .)com \
--cc=sunnanyong@huawei$(echo .)com \
--cc=surenb@google$(echo .)com \
--cc=thomas.hellstrom@linux$(echo .)intel.com \
--cc=tiwai@suse$(echo .)de \
--cc=usamaarif642@gmail$(echo .)com \
--cc=vbabka@suse$(echo .)cz \
--cc=vishal.moola@gmail$(echo .)com \
--cc=wangkefeng.wang@huawei$(echo .)com \
--cc=will@kernel$(echo .)org \
--cc=willy@infradead$(echo .)org \
--cc=yang@os$(echo .)amperecomputing.com \
--cc=ying.huang@linux$(echo .)alibaba.com \
--cc=ziy@nvidia$(echo .)com \
--cc=zokeefe@google$(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