From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Yunhui Cui <cuiyunhui@bytedance.com>
Cc: akpm@linux-foundation.org, liam@infradead.org, vbabka@kernel.org,
jannh@google.com, 00moses.alexander00@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/madvise: avoid skipping pages after splitting large folios
Date: Thu, 6 Aug 2026 13:35:30 +0200 [thread overview]
Message-ID: <919b804b-6f1d-417e-9c0c-d06f50d765d8@kernel.org> (raw)
In-Reply-To: <anQyoZgi5Urnvvjw@lucifer>
>
> Let's at least split out the folio check into a helper to make things
> clearer:
>
> static bool poison_splits_folio(const struct folio *folio)
> {
> /* Hugetlb is, as always, a world unto itself. */
> if (folio_test_hugetlb(folio))
> return false;
> /* Soft-offline errors out, hwpoison traverse DAX intact. */
> if (folio_is_zone_device(folio))
> return false;
> return true;
> }
>
> Then for your patch:
>
> - size = PAGE_SIZE;
> - if (folio_test_hugetlb(folio) || folio_is_zone_device(folio))
> - size = folio_size(folio);
> + size = poison_splits_folio(folio) ? PAGE_SIZE : folio_size(folio);
>
> I tried writing something that was neater and nicer but AI kept pointing
> out how it was totally broken and I really really hate this code (not your
> fault :).
No, I don't think any such special casing on folios is the right way to handle it.
--
Cheers,
David
next prev parent reply other threads:[~2026-08-06 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 5:55 [PATCH v2] mm/madvise: avoid skipping pages after splitting large folios Yunhui Cui
2026-08-06 6:29 ` Andrew Morton
2026-08-06 8:19 ` [External] " yunhui cui
2026-08-06 8:41 ` David Hildenbrand (Arm)
2026-08-06 9:13 ` Lorenzo Stoakes (ARM)
2026-08-06 9:11 ` Lorenzo Stoakes (ARM)
2026-08-06 11:35 ` David Hildenbrand (Arm) [this message]
2026-08-06 14:34 ` Lorenzo Stoakes (ARM)
2026-08-06 14:46 ` David Hildenbrand (Arm)
2026-08-06 15:40 ` Lorenzo Stoakes (ARM)
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=919b804b-6f1d-417e-9c0c-d06f50d765d8@kernel.org \
--to=david@kernel.org \
--cc=00moses.alexander00@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cuiyunhui@bytedance.com \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@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