From: Christoph Hellwig <hch@lst.de>
To: Anuj Gupta <anuj1072538@gmail.com>
Cc: asml.silence@gmail.com, hch@lst.de, djwong@kernel.org,
cem@kernel.org, brauner@kernel.org, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, joshi.k@samsung.com,
anuj20.g@samsung.com, nj.shetty@samsung.com
Subject: Re: [RFC 4/4] xfs: support dma-buf registered buffers for direct I/O
Date: Fri, 16 Oct 2026 11:28:55 +0200 [thread overview]
Message-ID: <20261016092855.GD23141@lst.de> (raw)
In-Reply-To: <20261016091919.971295-5-anuj1072538@gmail.com>
On Fri, Oct 16, 2026 at 02:49:14PM +0530, Anuj Gupta wrote:
> From: Nitesh Shetty <nj.shetty@samsung.com>
>
> Add the init_dma_buf_io_ctx fop for XFS files.
> XFS picks the device and calls the iomap layer with
> the relevant device.
>
> Refuse the iterator from every CPU-copy path: DAX, buffered
> fallback from a -ENOTBLK direct write, and read/writes
> without O_DIRECT.
>
> If a file is switched between the data and realtime devices
> after registration, the block layer cross-device check refuses
> the I/O.
>
> Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com>
> ---
> fs/xfs/xfs_file.c | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 426a67b813a7..f97d5acfaf68 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -340,6 +340,11 @@ xfs_file_read_iter(
> if (xfs_is_shutdown(mp))
> return -EIO;
>
> + /* a device mapping can only be read by a direct I/O bio */
> + if (iov_iter_is_dmabuf_map(to) &&
> + (IS_DAX(inode) || !(iocb->ki_flags & IOCB_DIRECT)))
> + return -EOPNOTSUPP;
Maybe move this into the actual methods for dax/buffered instead
to avoid extra conditionals? Same for the write side.
>
> @@ -1209,6 +1219,9 @@ xfs_file_write_iter(
> ret = xfs_file_dio_write(iocb, from);
> if (ret != -ENOTBLK)
> return ret;
> + /* the page cache cannot copy from a device mapping */
> + if (iov_iter_is_dmabuf_map(from))
> + return -EOPNOTSUPP;
I suspect these random fallbacks are going to cause trouble, but
I'm not really sure what to do about it either.
> +/*
> + * A realtime file's data lives on the realtime device, anything else on the
> + * data device. If a file is switched between them after registration, the
> + * block layer cross-device check refuses the I/O.
> + */
> +static int
> +xfs_file_init_dma_buf_io_ctx(
> + struct file *file,
> + struct dma_buf_io_ctx *ctx)
> +{
> + struct xfs_inode *ip = XFS_I(file_inode(file));
> +
> + return iomap_file_init_dma_buf_io_ctx(file,
> + xfs_inode_buftarg(ip)->bt_bdev, ctx);
> +}
Ah, this is where the previous cross check comes from. What about
simply disallowing toggling the RT flag with outstanding reservations
instead?
prev parent reply other threads:[~2026-10-16 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:19 [RFC 0/4] fs: support dma-buf backed direct I/O Anuj Gupta
2026-10-16 9:19 ` [RFC 1/4] block: factor out bdev_init_dma_buf_io_ctx() Anuj Gupta
2026-10-16 9:23 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 2/4] block: refuse a dma-buf bio for a disk the buffer was not registered on Anuj Gupta
2026-10-16 9:24 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 3/4] iomap: add dma-buf direct I/O guards and registration helper Anuj Gupta
2026-10-16 9:26 ` Christoph Hellwig
2026-10-16 9:19 ` [RFC 4/4] xfs: support dma-buf registered buffers for direct I/O Anuj Gupta
2026-10-16 9:28 ` Christoph Hellwig [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=20261016092855.GD23141@lst.de \
--to=hch@lst.de \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nj.shetty@samsung.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.