From: Mengmeng Zhao <mengmeng.zhao@linux.dev>
To: Jens Axboe <axboe@kernel.dk>, Dan Williams <djbw@kernel.org>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
tytso@mit.edu, Andreas Dilger <adilger.kernel@dilger.ca>,
Baokun Li <libaokun@linux.alibaba.com>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Zhang Yi <yi.zhang@huawei.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
asml.silence@gmail.com, hch@lst.de,
Anuj Gupta <anuj1072538@gmail.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, Li Wang <liwang@kylinos.cn>
Subject: [RFC 0/6] ext4: Add dma-buf read/write support
Date: Thu, 5 Nov 2026 14:58:41 +0800 [thread overview]
Message-ID: <20261105065847.196540-1-mengmeng.zhao@linux.dev> (raw)
From: Mengmeng Zhao <zhaomengmeng@kylinos.cn>
This series add dma-buf read/write support for ext4. The dma-buf direct
I/O infrastructure allows dma-buf to be handed to file I/O as an iov_iter,
currently it only supports raw device. To better serve the GPU-NVME direct
access through normal filesystem, prior work for XFS has been discussed
at [1]. We also are interested in this field and working on it[2]. This
patchset is based on Anuj Gupta's patchset as there are common parts at
block/iomap. The base tree is:
https://github.com/anuj7781/linux-kernel/tree/anuj/fs-dmabuf-rfc-v11-desc-v2
Patches 1-5 add dma-buf guards at several common paths at block,
mm/filemap, dax and iomap. Patches 6 add dma-buf support for ext4.
[1] https://lore.kernel.org/linux-xfs/20261016091919.971295-1-anuj1072538@gmail.com/
[2] https://lore.kernel.org/all/20260908131545.105987-1-liwang@kylinos.cn/
Mengmeng Zhao (6):
block: refuse a dma-buf bio that carries a crypto context
mm/filemap: refuse dmabuf iterators in the generic read/write copy
paths
dax: refuse dmabuf iterators in dax_iomap_rw()
iomap: refuse dmabuf iterators in iomap_file_buffered_write()
iomap: refuse dmabuf iterators on contents-encrypted inodes
ext4: support dma-buf registered buffers for direct I/O
block/blk-mq.c | 4 +++-
fs/dax.c | 4 ++++
fs/ext4/file.c | 33 +++++++++++++++++++++++++++++++++
fs/iomap/buffered-io.c | 7 +++++++
fs/iomap/direct-io.c | 10 ++++++++++
mm/filemap.c | 22 +++++++++++++++++++++-
6 files changed, 78 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-05 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 6:58 Mengmeng Zhao [this message]
2026-11-05 6:58 ` [RFC 1/6] block: refuse a dma-buf bio that carries a crypto context Mengmeng Zhao
2026-11-06 10:41 ` Christoph Hellwig
2026-11-09 2:51 ` Mengmeng Zhao
2026-11-05 6:58 ` [RFC 2/6] mm/filemap: refuse dmabuf iterators in the generic read/write copy paths Mengmeng Zhao
2026-11-06 10:42 ` Christoph Hellwig
2026-11-09 2:54 ` Mengmeng Zhao
2026-11-05 6:58 ` [RFC 3/6] dax: refuse dmabuf iterators in dax_iomap_rw() Mengmeng Zhao
2026-11-05 6:58 ` [RFC 4/6] iomap: refuse dmabuf iterators in iomap_file_buffered_write() Mengmeng Zhao
2026-11-05 6:58 ` [RFC 5/6] iomap: refuse dmabuf iterators on contents-encrypted inodes Mengmeng Zhao
2026-11-06 10:44 ` Christoph Hellwig
2026-11-09 2:56 ` Mengmeng Zhao
2026-11-05 6:58 ` [RFC 6/6] ext4: support dma-buf registered buffers for direct I/O Mengmeng Zhao
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=20261105065847.196540-1-mengmeng.zhao@linux.dev \
--to=mengmeng.zhao@linux.dev \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=anuj1072538@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djbw@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=libaokun@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=liwang@kylinos.cn \
--cc=nvdimm@lists.linux.dev \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.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 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.