From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: David Hildenbrand <david@redhat.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
sparclinux@vger.kernel.org, davem@davemloft.net,
andreas@gaisler.com
Cc: linux-kernel@vger.kernel.org, agordeev@linux.ibm.com,
will@kernel.org, ryan.roberts@arm.com, osalvador@suse.de
Subject: Re: [PATCH] sparc64: fix hugetlb for sun4u
Date: Mon, 11 Aug 2025 10:28:26 +0200 [thread overview]
Message-ID: <50eae15fb7ec8c6caa70811f231d69ef6f65e862.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <96992842-f576-4e19-afcb-7455452fe506@redhat.com>
Hi David,
thanks a lot for your input!
On Mon, 2025-08-11 at 10:20 +0200, David Hildenbrand wrote:
> On 09.08.25 08:23, John Paul Adrian Glaubitz wrote:
> > Hi Anthony,
> >
> > On Sat, 2025-08-09 at 00:37 +0200, John Paul Adrian Glaubitz wrote:
> > > > Maybe try enabling CONFIG_DEBUG_VM_IRQSOFF, CONFIG_DEBUG_VM, and perhaps
> > > > CONFIG_DEBUG_VM_PGFLAGS. That might help detect a problem closer to the
> > > > source. You can also try adding transparent_hugepage=never to the kernel
> > > > boot line to see if compiling in THP support but not using it is okay.
> > >
> > > OK, I will try that. But not today anymore. It's half past midnight now here in Germany
> > > and I was debugging this issue almost all day long. I'm glad to have finally been able
> > > to track this down to THP support being enabled.
> > >
> > > Maybe you can try whether you can reproduce this in QEMU as well.
> >
> > OK, first data point: Setting CONFIG_TRANSPARENT_HUGEPAGE_NEVER=y causes the backtrace during
> > boot to disappear with CONFIG_TRANSPARENT_HUGEPAGE=y. However, it still disappears later when
> > running "apt update && apt -y upgrade" again:
>
> Just to give some context: (m)THPs in file systems will get used
> independently of CONFIG_TRANSPARENT_HUGEPAGE_NEVER=y.
>
> So CONFIG_TRANSPARENT_HUGEPAGE_NEVER=y primarily only controls usage of
> (m)THPs for anonymous memory, but not in the pagecache.
Thanks, this actually explains why CONFIG_TRANSPARENT_HUGEPAGE_NEVER=y doesn't fully mitigate
the problem.
> > [ 170.472743] kernel BUG at fs/ext4/inode.c:1174!
> > [ 170.532313] \|/ ____ \|/
> > "@'/ .. \`@"
> > /_| \__/ |_\
> > \__U_/
>
> Is this the
>
> BUG_ON(to > folio_size(folio));
Yes, I just looked it up in my current local kernel tree and that's indeed the line.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2025-08-11 8:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 1:24 Anthony Yznaga
2025-07-16 6:18 ` John Paul Adrian Glaubitz
2025-07-16 8:41 ` John Paul Adrian Glaubitz
2025-07-16 16:47 ` Anthony Yznaga
2025-07-24 10:52 ` John Paul Adrian Glaubitz
2025-07-25 5:59 ` John Paul Adrian Glaubitz
2025-07-25 20:46 ` John Paul Adrian Glaubitz
2025-07-25 21:09 ` John Paul Adrian Glaubitz
2025-08-08 21:31 ` John Paul Adrian Glaubitz
2025-08-08 22:15 ` Anthony Yznaga
2025-08-08 22:37 ` John Paul Adrian Glaubitz
2025-08-09 6:23 ` John Paul Adrian Glaubitz
2025-08-09 6:26 ` John Paul Adrian Glaubitz
2025-08-09 6:42 ` John Paul Adrian Glaubitz
2025-08-10 9:52 ` John Paul Adrian Glaubitz
2025-08-10 22:20 ` John Paul Adrian Glaubitz
2025-08-11 8:25 ` David Hildenbrand
2025-08-11 10:44 ` John Paul Adrian Glaubitz
2025-08-11 11:06 ` John Paul Adrian Glaubitz
2025-08-12 12:32 ` Found it - was: " John Paul Adrian Glaubitz
2025-08-12 12:34 ` John Paul Adrian Glaubitz
2025-08-21 12:52 ` David Hildenbrand
2025-08-21 15:03 ` Edgecombe, Rick P
2025-08-21 16:42 ` John Paul Adrian Glaubitz
2025-08-11 8:20 ` David Hildenbrand
2025-08-11 8:28 ` John Paul Adrian Glaubitz [this message]
2025-09-19 18:01 ` Andreas Larsson
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=50eae15fb7ec8c6caa70811f231d69ef6f65e862.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=agordeev@linux.ibm.com \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=ryan.roberts@arm.com \
--cc=sparclinux@vger.kernel.org \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®