public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Anuj Gupta <anuj20.g@samsung.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	io-uring@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: io_uring / dio metadata fixes
Date: Wed, 20 Aug 2025 11:13:28 +0200	[thread overview]
Message-ID: <20250820-beckenrand-anbringen-b821987f39be@brauner> (raw)
In-Reply-To: <20250819082517.2038819-1-hch@lst.de>

On Tue, 19 Aug 2025 10:24:59 +0200, Christoph Hellwig wrote:
> while trying to add XFS support for passing through metadata I ran
> into a few issues with how that support is wire up for the current
> block device use cases, and this fixes it.
> 
> Diffstat:
>  block/fops.c       |   13 ++++++++-----
>  include/linux/fs.h |    3 ++-
>  io_uring/rw.c      |    3 +++
>  3 files changed, 13 insertions(+), 6 deletions(-)
> 
> [...]

Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes

[1/2] fs: add a FMODE_ flag to indicate IOCB_HAS_METADATA availability
      https://git.kernel.org/vfs/vfs/c/d072148a8631
[2/2] block: don't silently ignore metadata for sync read/write
      https://git.kernel.org/vfs/vfs/c/2729a60bbfb9

      parent reply	other threads:[~2025-08-20  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  8:24 io_uring / dio metadata fixes Christoph Hellwig
2025-08-19  8:25 ` [PATCH 1/2] fs: add a FMODE_ flag to indicate IOCB_HAS_METADATA availability Christoph Hellwig
2025-08-19  9:14   ` Christian Brauner
2025-08-19  9:22     ` Christoph Hellwig
2025-08-19 10:14       ` Christian Brauner
2025-08-19 13:34         ` Christoph Hellwig
2025-08-20  9:40           ` Christian Brauner
2025-08-21  8:42             ` Christoph Hellwig
2025-08-25 12:01               ` Christian Brauner
2025-08-25 13:35                 ` Christoph Hellwig
2025-08-19  8:25 ` [PATCH 2/2] block: don't silently ignore metadata for sync read/write Christoph Hellwig
2025-08-20  3:23   ` Martin K. Petersen
2025-08-20  9:13 ` Christian Brauner [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=20250820-beckenrand-anbringen-b821987f39be@brauner \
    --to=brauner@kernel.org \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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