Linux block layer
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
	djwong@kernel.org, axboe@kernel.dk, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] iomap: don't make REQ_POLLED imply REQ_NOWAIT
Date: Mon, 18 May 2026 14:23:16 +0200	[thread overview]
Message-ID: <20260518-tattoo-brannten-c5b64728e6ca@brauner> (raw)
In-Reply-To: <20260518062917.506483-1-hch@lst.de>

On Mon, 18 May 2026 08:29:13 +0200, Christoph Hellwig wrote:
> As described in commit 2bc057692599 ("block: don't make REQ_POLLED imply
> REQ_NOWAIT"), which fixed the same issue for the block device node, there
> are valid cases to poll for I/O completion without REQ_NOWAIT.
> 
> Additionally, sing REQ_NOWAIT for file system writes is currently not
> supported as file systems writes are not idempotent and would need a
> retry of just the bio and not the entire operation to be fully supported.
> 
> [...]

Applied to the vfs-7.2.iomap branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.iomap 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-7.2.iomap

[1/1] iomap: don't make REQ_POLLED imply REQ_NOWAIT
      https://git.kernel.org/vfs/vfs/c/47f28b493daf

      reply	other threads:[~2026-05-18 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  6:29 [PATCH] iomap: don't make REQ_POLLED imply REQ_NOWAIT Christoph Hellwig
2026-05-18 12:23 ` 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=20260518-tattoo-brannten-c5b64728e6ca@brauner \
    --to=brauner@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox