From: David Sterba <dsterba@suse.cz>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix unnecessary increment of read error stat on write error
Date: Mon, 20 Feb 2023 21:04:53 +0100 [thread overview]
Message-ID: <20230220200453.GF10580@twin.jikos.cz> (raw)
In-Reply-To: <29145a990313cb8759b8131b07f29694cc183ab3.1676265001.git.naohiro.aota@wdc.com>
On Mon, Feb 13, 2023 at 02:10:38PM +0900, Naohiro Aota wrote:
> Current btrfs_log_dev_io_error() increases the read error count even if the
> erroneous IO is a WRITE request. This is because it forget to use "else
> if", and all the error WRITE requests counts as READ error as there is (of
> course) no REQ_RAHEAD bit set.
>
> Fixes: c3a62baf21ad ("btrfs: use chained bios when cloning")
> CC: stable@vger.kernel.org # 6.1
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Added to misc-next, thanks.
prev parent reply other threads:[~2023-02-20 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 5:10 [PATCH] btrfs: fix unnecessary increment of read error stat on write error Naohiro Aota
2023-02-13 6:42 ` Christoph Hellwig
2023-02-13 7:55 ` Johannes Thumshirn
2023-02-20 20:04 ` David Sterba [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=20230220200453.GF10580@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=stable@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