From: Shivank Garg <shivankg@amd.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: shaggy@kernel.org, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.com
Subject: Re: [PATCH] jfs: implement migrate_folio for jfs_metapage_aops
Date: Mon, 14 Apr 2025 10:23:04 +0530 [thread overview]
Message-ID: <255c8ef4-d47a-4559-9c85-c246855347c9@amd.com> (raw)
In-Reply-To: <Z_whZHPR64FHq6ve@casper.infradead.org>
On 4/14/2025 2:11 AM, Matthew Wilcox wrote:
> On Sun, Apr 13, 2025 at 05:23:57PM +0000, Shivank Garg wrote:
>> +++ b/fs/jfs/jfs_metapage.c
>> @@ -570,6 +570,7 @@ const struct address_space_operations jfs_metapage_aops = {
>> .release_folio = metapage_release_folio,
>> .invalidate_folio = metapage_invalidate_folio,
>> .dirty_folio = filemap_dirty_folio,
>> + .migrate_folio = filemap_migrate_folio,
>> };
>
> Ooh, damn, I think we're going to need more than this ;-(
>
> static inline struct metapage *folio_to_mp(struct folio *folio, int offset)
> {
> return folio->private;
> }
>
> struct metapage {
> ...
> void *data; /* Data pointer */
>
> So we're going to need something like buffer_migrate_folio(), but
> specialised to jfs metadata. And when we come up with it, that'll
> be Fixes: 35474d52c605
Thanks for the pointers. I missed the private data aspect earlier.
I think it's doable - IIUC, I'll need to
update mp->folio and mp->data to point to the dst folio info.
I'll work on a patch for it.
Best Regards,
Shivank
next prev parent reply other threads:[~2025-04-14 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 17:23 Shivank Garg
2025-04-13 20:41 ` Matthew Wilcox
2025-04-14 4:53 ` Shivank Garg [this message]
2025-04-14 13:10 ` Shivank Garg
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=255c8ef4-d47a-4559-9c85-c246855347c9@amd.com \
--to=shivankg@amd.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®