From: Matthew Wilcox <willy@infradead.org>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: get rid of buffer_head use
Date: Fri, 7 Jun 2024 14:33:03 +0100 [thread overview]
Message-ID: <ZmMMDy9eeCU2igqj@casper.infradead.org> (raw)
In-Reply-To: <20240607101829.389015-1-chao@kernel.org>
On Fri, Jun 07, 2024 at 06:18:29PM +0800, Chao Yu wrote:
> @@ -1990,6 +1989,12 @@ static inline struct f2fs_super_block *F2FS_RAW_SUPER(struct f2fs_sb_info *sbi)
> return (struct f2fs_super_block *)(sbi->raw_super);
> }
>
> +static inline struct f2fs_super_block *F2FS_SUPER_BLOCK(struct folio *folio)
> +{
> + return (struct f2fs_super_block *)(page_address(folio_page(folio, 0)) +
> + F2FS_SUPER_OFFSET);
> +}
This assumes that the superblock is in the first page of the folio.
That's not necessarily guaranteed; let's say you have a 64KiB folio
that covers the start of the bdev.
I don't quite know how to write this because f2fs defines its block size
in terms of PAGE_SIZE, which just seems like nonsense to me. If you
format a filesystem on a 16KiB PAGE_SIZE machine and then try to mount
it on a machine with a 4KiB PAGE_SIZE, it's going to go horribly wrong.
You'd need to pass in something that indicates whether you're trying to
access the first or second superblock; there's no way to tell from the
folio which one it is.
> +static int __f2fs_commit_super(struct f2fs_sb_info *sbi, struct folio *folio,
> + bool update)
> {
> - lock_buffer(bh);
> - if (super)
> - memcpy(bh->b_data + F2FS_SUPER_OFFSET, super, sizeof(*super));
> - set_buffer_dirty(bh);
> - unlock_buffer(bh);
> -
> + struct bio *bio;
> /* it's rare case, we can do fua all the time */
> - return __sync_dirty_buffer(bh, REQ_SYNC | REQ_PREFLUSH | REQ_FUA);
> + blk_opf_t opf = REQ_OP_WRITE | REQ_SYNC | REQ_PREFLUSH | REQ_FUA;
> + int ret;
> +
> + folio_lock(folio);
> + folio_wait_writeback(folio);
> + if (update)
> + memcpy(F2FS_SUPER_BLOCK(folio), F2FS_RAW_SUPER(sbi),
> + sizeof(struct f2fs_super_block));
> + folio_mark_dirty(folio);
> + folio_clear_dirty_for_io(folio);
> + folio_start_writeback(folio);
> + folio_unlock(folio);
> +
> + bio = bio_alloc(sbi->sb->s_bdev, 1, opf, GFP_NOFS);
> +
> + /* it doesn't need to set crypto context for superblock update */
> + bio->bi_iter.bi_sector = SECTOR_FROM_BLOCK(folio_index(folio));
> +
> + if (!bio_add_folio(bio, folio, PAGE_SIZE, 0))
> + f2fs_bug_on(sbi, 1);
Better make that folio_size(folio) to support bs>PS.
next prev parent reply other threads:[~2024-06-07 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:18 [PATCH v2] f2fs: get rid of buffer_head use Chao Yu
2024-06-07 13:33 ` Matthew Wilcox [this message]
2024-06-07 14:10 ` Chao Yu
2024-06-07 16:02 ` Matthew Wilcox
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=ZmMMDy9eeCU2igqj@casper.infradead.org \
--to=willy@infradead.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).