From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kiryl Shutsemau <kirill@shutemov.name>
Cc: Zi Yan <ziy@nvidia.com>, Hao Zhang <hao_zhang_kdev@163.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: thp: unlock i_mmap before releasing split folios
Date: Tue, 14 Jul 2026 14:34:38 +0200 [thread overview]
Message-ID: <be0ada61-9a44-4493-aff6-eab4a5049e90@kernel.org> (raw)
In-Reply-To: <alYoARy80Vb-X_nj@thinkstation>
On 7/14/26 14:17, Kiryl Shutsemau wrote:
> On Tue, Jul 14, 2026 at 01:29:56PM +0200, David Hildenbrand (Arm) wrote:
>>> Any opinions?
>>
>> I guess a deferred iput through some workqueue is not an option?
>
> Hm. This feels like a dirty hack to me.
>
>> I'd prefer if we could keep folio splitting working even when the passed page is
>> EOF.
>
> Can you think of legitimate use-case?
>
> I will get rid of hwpoison case. It has no good reason to lock tail page
> in the first place.
If we can get that out of the way, fine with me.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-14 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:13 [PATCH] mm: thp: unlock i_mmap before releasing split folios Hao Zhang
2026-07-10 11:16 ` Kiryl Shutsemau
2026-07-10 15:56 ` Hao Zhang
2026-07-10 17:04 ` Lorenzo Stoakes
2026-07-10 17:17 ` Kiryl Shutsemau
2026-07-14 2:12 ` Zi Yan
2026-07-14 2:15 ` Zi Yan
2026-07-14 3:44 ` Baolin Wang
2026-07-14 10:26 ` Kiryl Shutsemau
2026-07-14 11:29 ` David Hildenbrand (Arm)
2026-07-14 12:17 ` Kiryl Shutsemau
2026-07-14 12:34 ` David Hildenbrand (Arm) [this message]
2026-07-14 9:33 ` Hao Zhang
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=be0ada61-9a44-4493-aff6-eab4a5049e90@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hao_zhang_kdev@163.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.