btrfs: don't report readahead errors and don't update statistics
authorDavid Sterba <dsterba@suse.com>
Thu, 7 Mar 2019 14:40:50 +0000 (15:40 +0100)
committerDavid Sterba <dsterba@suse.com>
Wed, 13 Mar 2019 16:14:27 +0000 (17:14 +0100)
commit0cc068e6ee59c1fffbfa977d8bf868b7551d80ac
tree9bde1d25ac327204fca4cb8f5f058bd109122197
parent609e804d771f59dc5d45a93e5ee0053c74bbe2bf
btrfs: don't report readahead errors and don't update statistics

As readahead is an optimization, all errors are usually filtered out,
but still properly handled when the real read call is done. The commit
5e9d398240b2 ("btrfs: readpages() should submit IO as read-ahead") added
REQ_RAHEAD to readpages() because that's only used for readahead
(despite what one would expect from the callback name).

This causes a flood of messages and inflated read error stats, so skip
reporting in case it's readahead.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202403
Reported-by: LimeTech <tomm@lime-technology.com>
Fixes: 5e9d398240b2 ("btrfs: readpages() should submit IO as read-ahead")
CC: stable@vger.kernel.org # 4.19+
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/volumes.c