From: Christoph Hellwig <hch@lst.de>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>, Dave Kleikamp <shaggy@kernel.org>,
Jan Kara <jack@suse.com>, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, ocfs2-devel@lists.linux.dev
Subject: Re: removing the remaining blockdev_direct_IO users
Date: Mon, 13 Jul 2026 11:58:57 +0200 [thread overview]
Message-ID: <20260713095857.GB10501@lst.de> (raw)
In-Reply-To: <fea4c4f25afb7711d1e8fbe6ca5ab654ec522186.camel@dubeyko.com>
On Fri, Jul 10, 2026 at 09:51:09AM -0700, Viacheslav Dubeyko wrote:
> On Fri, 2026-07-10 at 07:07 +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > we have 7 users of blockdev_direct_IO and one of the lower-level
> > __blockdev_direct_IO left, and I'd really like to get rid of them.
> >
> > The filesystems are affs, fat, hfs, hfsplus, jfs, nilfs2, udf and
> > ocfs2,
> > and you are the relevant maintainers. In 7.2 exfat converted
> > entirely
> > to iomap, which would be a really good example for a "simple" file
> > system. Another options especially for the file systems supporting
> > foreign formats would be to just drop direct I/O support and reduce
> > the support burden.
>
> I like the idea. I think we can try to switch HFS/HFS+ and NILFS2 on
> iomap approach. Do you have some initial patches for this? Which
> particular commit(s) converted the exfat to iomap? It will be good to
> take a deeper look into this conversion to estimate the complexity of
> HFS/HFS+, NILFS2 modifications.
Almost all commits in fs/exfat/ in 7.2-rc1, starting with
623f0aa1eca5c2a94ca1e4e5de719d062eac3b6c
next prev parent reply other threads:[~2026-07-13 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:07 removing the remaining blockdev_direct_IO users Christoph Hellwig
2026-07-10 16:51 ` Viacheslav Dubeyko
2026-07-13 9:58 ` Christoph Hellwig [this message]
2026-07-13 22:33 ` Viacheslav Dubeyko
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=20260713095857.GB10501@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=shaggy@kernel.org \
--cc=slava@dubeyko.com \
/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