mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	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:25:03 +0200	[thread overview]
Message-ID: <f358f3ce-1140-4dd1-a1b8-379563c5f050@redhat.com> (raw)
In-Reply-To: <2bcb018c8b237f7ab2356f4459e14ae81a6fec8b.camel@physik.fu-berlin.de>

On 11.08.25 00:20, John Paul Adrian Glaubitz wrote:
> Hi,
> 
> On Sun, 2025-08-10 at 11:52 +0200, John Paul Adrian Glaubitz wrote:
>> On Sat, 2025-08-09 at 08:42 +0200, John Paul Adrian Glaubitz wrote:
>>> Let me know if you have more suggestions to test. I can also provide you with full
>>> access to this Netra 240 if you send me your public SSH key in a private mail.
>>
>> I have narrowed it down to a regression between v6.3 and v6.4 now.
>>
>> The bug can be reproduced with the sparc64_defconfig on a Sun Netra 240 by setting
>> CONFIG_TRANSPARENT_HUGEPAGE=y and CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y. When testing
>> on a modern systemd-based distribution, it's also necessary to enable CGroup support
>> as well as enable support for Sun partition tables with CONFIG_SUN_PARTITION=y.
>>
>> Then it should be a matter of bisecting the commits between v6.3 and v6.4.
>>
>> I will do that within the next days as I'm currently a bit busy with other stuff.
> 
> OK, it turns out it's reproducible on older kernels (but not as old as 4.19) as well.
> It's just much harder to trigger. I found a reproducer though and will try to find
> the problematic commit next.

ext4 support for large folios was added recently (6.16? not 100% sure).

But below can indicate some ext4 issue with large folios. 
(fault:filemap_fault mmap:ext4_file_mmap)

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2025-08-11  8:25 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 [this message]
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
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=f358f3ce-1140-4dd1-a1b8-379563c5f050@redhat.com \
    --to=david@redhat.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andreas@gaisler.com \
    --cc=anthony.yznaga@oracle.com \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --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®