From: David Hildenbrand <david@redhat.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
Shakeel Butt <shakeel.butt@linux.dev>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@kernel.org,
zhengqi.arch@bytedance.com, lorenzo.stoakes@oracle.com,
hughd@google.com, willy@infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH v2 1/2] mm: vmscan: remove folio_test_private() check in pageout()
Date: Fri, 19 Sep 2025 10:00:06 +0200 [thread overview]
Message-ID: <db051a89-4eef-42c1-9fd2-16ffbad18b75@redhat.com> (raw)
In-Reply-To: <787dc1a4-d0b7-4559-8160-55de987beac3@linux.alibaba.com>
>>>>> - if (folio_test_private(folio)) {
>>>>> - if (try_to_free_buffers(folio)) {
>>>>> - folio_clear_dirty(folio);
>>>>> - pr_info("%s: orphaned folio\n", __func__);
>>>>> - return PAGE_CLEAN;
>>>>> - }
>>>>> - }
>>>>> + VM_WARN_ON_FOLIO(true, folio);
>>
>> Unexpected but better to use VM_WARN_ON_ONCE_FOLIO here.
>
> Um, I don't think it makes much difference, because we should no longer
> hit this.
I mean, all VM_WARN_ON are not expected to be hit. But if it ever
happens, it's usually going to be a lot.
(I recall Lorenzo wanted to look into cleaning a lot of that up and
possibly unifying both helpers)
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-09-19 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 3:46 [PATCH v2 0/2] some cleanups for pageout() Baolin Wang
2025-09-18 3:46 ` [PATCH v2 1/2] mm: vmscan: remove folio_test_private() check in pageout() Baolin Wang
2025-09-18 6:00 ` David Hildenbrand
2025-09-18 9:36 ` Baolin Wang
2025-09-19 1:06 ` Shakeel Butt
2025-09-19 2:12 ` Baolin Wang
2025-09-19 8:00 ` David Hildenbrand [this message]
2025-09-22 5:32 ` Hugh Dickins
2025-09-22 6:02 ` Baolin Wang
2025-09-18 3:46 ` [PATCH v2 2/2] mm: vmscan: simplify the folio refcount " Baolin Wang
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=db051a89-4eef-42c1-9fd2-16ffbad18b75@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox