From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>, Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org,
Joanne Koong <joannelkoong@gmail.com>,
linux-mm@kvack.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 06/11] migrate: Remove call to ->writepage
Date: Tue, 1 Apr 2025 15:32:15 +0200 [thread overview]
Message-ID: <cdca1510-7b8e-4fa0-a3aa-c66ea224f400@redhat.com> (raw)
In-Reply-To: <D8R80OMV06HN.2MXFKF6L5851V@nvidia.com>
On 27.03.25 18:22, Zi Yan wrote:
> On Thu Mar 27, 2025 at 12:52 PM EDT, Matthew Wilcox wrote:
>> On Thu, Mar 27, 2025 at 11:04:57AM -0400, Zi Yan wrote:
>>> On Fri Mar 7, 2025 at 8:54 AM EST, Matthew Wilcox (Oracle) wrote:
>>>> The writepage callback is going away; filesystems must implement
>>>> migrate_folio or else dirty folios will not be migratable.
>>>
>>> What is the impact of this? Are there any filesystem that has
>>> a_ops->writepage() without migrate_folio()? I wonder if it could make
>>> the un-migratable problem worse[1] when such FS exists.
>>
>> As Christoph and I have been going through filesystems removing their
>> ->writepage operations, we've been careful to add ->migrate_folio
>> callbacks at the same time. But we haven't fixed any out-of-tree
>> filesystems, and we can't fix the filesystems which will be written in
>> the future.
>>
>> So maybe what we should do is WARN_ON_ONCE() for filesystems which
>> have a ->writepages, but do not have a ->migrate_folio()?
>
> Sounds good to me.
Agreed, that will also make it clear what our expectation towards
filesystems is.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-01 13:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:54 [PATCH 00/11] Remove aops->writepage Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 01/11] f2fs: Remove check for ->writepage Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 02/11] f2fs: Remove f2fs_write_data_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 03/11] f2fs: Remove f2fs_write_meta_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 04/11] f2fs: Remove f2fs_write_node_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 05/11] vboxsf: Convert to writepages Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 06/11] migrate: Remove call to ->writepage Matthew Wilcox (Oracle)
2025-03-27 15:04 ` Zi Yan
2025-03-27 16:52 ` Matthew Wilcox
2025-03-27 17:22 ` Zi Yan
2025-04-01 13:32 ` David Hildenbrand [this message]
2025-03-07 13:54 ` [PATCH 07/11] writeback: Remove writeback_use_writepage() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 08/11] shmem: Add shmem_writeout() Matthew Wilcox (Oracle)
2025-03-08 5:31 ` Baolin Wang
2025-03-07 13:54 ` [PATCH 09/11] i915: Use writeback_iter() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 10/11] mm: Remove swap_writepage() and shmem_writepage() Matthew Wilcox (Oracle)
2025-03-08 5:34 ` Baolin Wang
2025-03-07 13:54 ` [PATCH 11/11] fs: Remove aops->writepage Matthew Wilcox (Oracle)
2025-03-17 1:08 ` Fan Ni
2025-03-17 3:22 ` Matthew Wilcox
2025-03-17 22:30 ` Matthew Wilcox
2025-03-18 8:10 ` Thomas Hellström
2025-04-01 16:26 ` Matthew Wilcox
2025-05-02 14:33 ` Thomas Hellström
2025-03-28 9:40 ` [PATCH 00/11] " Christian Brauner
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=cdca1510-7b8e-4fa0-a3aa-c66ea224f400@redhat.com \
--to=david@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).