From: Matthew Wilcox <willy@infradead.org>
To: Johannes Thumshirn <jth@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-fsdevel@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH] zonefs: move super block reading from page to folio
Date: Thu, 23 May 2024 02:41:51 +0100 [thread overview]
Message-ID: <Zk6e30EMxz_8LbW6@casper.infradead.org> (raw)
In-Reply-To: <20240514152208.26935-1-jth@kernel.org>
On Tue, May 14, 2024 at 05:22:08PM +0200, Johannes Thumshirn wrote:
> From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>
> Move reading of the on-disk superblock from page to kmalloc()ed memory.
No, this is wrong.
> + super = kzalloc(ZONEFS_SUPER_SIZE, GFP_KERNEL);
> + if (!super)
> return -ENOMEM;
>
> + folio = virt_to_folio(super);
This will stop working at some point. It'll return NULL once we get
to the memdesc future (because the memdesc will be a slab, not a folio).
> bio_init(&bio, sb->s_bdev, &bio_vec, 1, REQ_OP_READ);
> bio.bi_iter.bi_sector = 0;
> - __bio_add_page(&bio, page, PAGE_SIZE, 0);
> + bio_add_folio_nofail(&bio, folio, ZONEFS_SUPER_SIZE,
> + offset_in_folio(folio, super));
It also doesn't solve the problem of trying to read 4KiB from a device
with 16KiB sectors. We'll have to fail the bio because there isn't
enough memory in the bio to store one block.
I think the right way to handle this is to call read_mapping_folio().
That will allocate a folio in the page cache for you (obeying the
minimum folio size). Then you can examine the contents. It should
actually remove code from zonefs. Don't forget to call folio_put()
when you're done with it (either at unmount or at the end of mount if
you copy what you need elsewhere).
next prev parent reply other threads:[~2024-05-23 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 15:22 [PATCH] zonefs: move super block reading from page to folio Johannes Thumshirn
2024-05-14 19:12 ` Bill O'Donnell
2024-05-23 1:41 ` Matthew Wilcox [this message]
2024-05-23 9:54 ` Johannes Thumshirn
2024-05-23 11:48 ` Matthew Wilcox
2024-05-23 11:49 ` Johannes Thumshirn
2024-05-31 1:16 ` Darrick J. Wong
2024-05-31 1:28 ` Damien Le Moal
2024-06-01 17:51 ` Matthew Wilcox
2024-06-03 0:30 ` Damien Le Moal
2024-06-04 5:33 ` Christoph Hellwig
2024-06-04 22:30 ` Damien Le Moal
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=Zk6e30EMxz_8LbW6@casper.infradead.org \
--to=willy@infradead.org \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=jth@kernel.org \
--cc=linux-fsdevel@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).