From: "Darrick J. Wong" <djwong@kernel.org>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: glaubitz@physik.fu-berlin.de, frank.li@vivo.com, hch@lst.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
vdubeyko@coreweave.com, willy@infradead.org, brauner@kernel.org
Subject: Re: [PATCH v3 0/7] hfsplus: convert regular file I/O to iomap-based operations
Date: Wed, 9 Sep 2026 09:51:05 -0700 [thread overview]
Message-ID: <20260909165105.GH127607@frogsfrogsfrogs> (raw)
In-Reply-To: <20260908210448.296772-1-slava@dubeyko.com>
On Tue, Sep 08, 2026 at 02:04:41PM -0700, Viacheslav Dubeyko wrote:
> This series moves HFS+ regular file data I/O off the legacy
> buffer_head/blockdev_direct_IO() path onto iomap-based operations with
> the goal to retire the older buffer_head-based direct I/O infrastructure.
>
> v2
> Christoph Hellwig has detected that taking the page lock around
> the kmap/modify/kunmap section is not enough on its own:
> writeback drops the page lock before the write actually completes,
> so a mutator that only waits on the lock can still start rewriting
> a page whose old contents are still in flight to the device.
> Mark the allocation file's mapping with mapping_set_stable_writes()
> and call folio_wait_stable() right after taking the page lock in
> both functions, so a mutator also waits out any writeback that was
> already in progress when it acquired the lock.
>
> Christoph Hellwig suggested to introduce a generalized version
> of iomap_dio_end_io() that was placed into include/linux/iomap.h.
>
> The hfsplus_btree_aops uses hfsplus_btree_read_folio() and
> hfsplus_btree_writepages() methods. The hfsplus_symlink_aops
> uses hfsplus_symlink_read_folio() and hfsplus_symlink_writepages()
> methods. Also, hfsplus_setattr() doesn't distinguish the regular
> and not regular file cases anymore.
>
> v3
> Matthew Wilcox recommended to use folio_wait_writeback()
> instead of folio_wait_stable().
>
> Fix failures in generic/091, generic/521, and generic/551.
FWIW the iomap port itself looks correct to me, so for patches 4, 6,
and 7:
Acked-by: "Darrick J. Wong" <djwong@kernel.org>
but my knowledge of HFS+ is pretty fragmented now, so I couldn't say for
sure about 1-3 or 5.
--D
> Viacheslav Dubeyko (7):
> hfs/hfsplus: exchange hardcoded number of extents on named constants
> hfsplus: rework hfsplus_get_block() logic
> hfsplus: take the bitmap page lock for allocate/free
> hfsplus: add iomap operations for regular file data
> hfsplus: move file related operations to file.c
> hfsplus: introduce iomap-based file_operations
> hfsplus: switch address_space_operations on iomap-based support
>
> fs/hfsplus/Kconfig | 2 +-
> fs/hfsplus/Makefile | 5 +-
> fs/hfsplus/bitmap.c | 18 +++
> fs/hfsplus/extents.c | 164 ++++++++++++++------
> fs/hfsplus/file.c | 304 +++++++++++++++++++++++++++++++++++++
> fs/hfsplus/hfsplus_fs.h | 26 +++-
> fs/hfsplus/inode.c | 281 ++++++++++------------------------
> fs/hfsplus/iomap.c | 192 +++++++++++++++++++++++
> fs/hfsplus/iomap.h | 18 +++
> include/linux/hfs_common.h | 8 +-
> include/linux/iomap.h | 20 +++
> 11 files changed, 787 insertions(+), 251 deletions(-)
> create mode 100644 fs/hfsplus/file.c
> create mode 100644 fs/hfsplus/iomap.c
> create mode 100644 fs/hfsplus/iomap.h
>
> --
> 2.43.0
>
prev parent reply other threads:[~2026-09-09 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 21:04 [PATCH v3 0/7] hfsplus: convert regular file I/O to iomap-based operations Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 1/7] hfs/hfsplus: exchange hardcoded number of extents on named constants Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 2/7] hfsplus: rework hfsplus_get_block() logic Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 3/7] hfsplus: take the bitmap page lock for allocate/free Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 4/7] hfsplus: add iomap operations for regular file data Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 5/7] hfsplus: move file related operations to file.c Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 6/7] hfsplus: introduce iomap-based file_operations Viacheslav Dubeyko
2026-09-08 21:04 ` [PATCH v3 7/7] hfsplus: switch address_space_operations on iomap-based support Viacheslav Dubeyko
2026-09-09 16:51 ` Darrick J. Wong [this message]
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=20260909165105.GH127607@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=vdubeyko@coreweave.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.