From: Christian Brauner <brauner@kernel.org>
To: djwong@kernel.org, Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
viro@zeniv.linux.org.uk, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com
Subject: Re: [PATCH] iomap: handle error conditions more gracefully in iomap_to_bh
Date: Wed, 6 Sep 2023 16:31:45 +0200 [thread overview]
Message-ID: <20230906-orangen-kurios-99d82ff11449@brauner> (raw)
In-Reply-To: <20230905124120.325518-1-hch@lst.de>
On Tue, 05 Sep 2023 14:41:20 +0200, Christoph Hellwig wrote:
> iomap_to_bh currently BUG()s when the passed in block number is not
> in the iomap. For file systems that have proper synchronization this
> should never happen and so far hasn't in mainline, but for block devices
> size changes aren't fully synchronized against ongoing I/O. Instead
> of BUG()ing in this case, return -EIO to the caller, which already has
> proper error handling. While we're at it, also return -EIO for an
> unknown iomap state instead of returning garbage.
>
> [...]
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc 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.misc
[1/1] iomap: handle error conditions more gracefully in iomap_to_bh
https://git.kernel.org/vfs/vfs/c/6f71eda85ab8
prev parent reply other threads:[~2023-09-06 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 12:41 [PATCH] iomap: handle error conditions more gracefully in iomap_to_bh Christoph Hellwig
2023-09-05 15:39 ` Darrick J. Wong
2023-09-05 15:53 ` Christoph Hellwig
2023-09-06 14:30 ` Christian Brauner
2023-09-06 14:54 ` Darrick J. Wong
2023-09-06 1:18 ` Damien Le Moal
2023-09-06 9:26 ` Hannes Reinecke
2023-09-06 14:31 ` 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=20230906-orangen-kurios-99d82ff11449@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=syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).