From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v3 11/12] ext4: Stop providing .writepage hook
Date: Mon, 5 Dec 2022 22:17:26 -0500 [thread overview]
Message-ID: <Y460RpKTCDuPKWmN@mit.edu> (raw)
In-Reply-To: <20221205122928.21959-11-jack@suse.cz>
On Mon, Dec 05, 2022 at 01:29:25PM +0100, Jan Kara wrote:
> Now we don't need .writepage hook for anything anymore. Reclaim is fine
> with relying on .writepages to clean pages and we often couldn't do much
> from the .writepage callback anyway. We only need to provide
> .migrate_folio callback for the ext4_journalled_aops - let's use
> buffer_migrate_page_norefs() there so that buffers cannot be modified
^^^^^^^^^^^^^^^^^^^^^^^^^^ this should be buffer_migrate_folio_norefs, no?
> under jdb2's hands.
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Jan Kara <jack@suse.cz>
Could you clarify in the commit how critical it is to use the
_norefs() variant? It's not entirely clear what you mean by "let's
use...". I think what is meant is that we need to use ..._noref() or
we can get in trouble if while the page update is getting committed,
there is an attempted to migrate the folio containing the page.
buffer_migrate_folio_norefs() is currently not exported (although
buffer_migrate_folio is). So if we need it for ext4, we're going to
have to EXPORT_SYMBOL buffer_migrate_folio_norefs.
Any objections from the mm folks?
- Ted
next parent reply other threads:[~2022-12-06 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221205122604.25994-1-jack@suse.cz>
[not found] ` <20221205122928.21959-11-jack@suse.cz>
2022-12-06 3:17 ` Theodore Ts'o [this message]
2022-12-06 10:52 ` Jan Kara
2022-12-07 7:38 ` Christoph Hellwig
2022-12-07 11:17 ` Jan Kara
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=Y460RpKTCDuPKWmN@mit.edu \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ritesh.list@gmail.com \
--cc=willy@infradead.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