diff options
| author | Mikulas Patocka <mpatocka@redhat.com> | 2018-09-05 16:14:36 -0600 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-09-19 22:41:20 +0200 |
| commit | d927dea6392d5445a62f104baf8881ff5095d3ba (patch) | |
| tree | b8e48219f8a7b4f03157dd66e8e218b63a36864f /block | |
| parent | 56935391aba9292b1b6a30e81c4f42495b3120b7 (diff) | |
| download | linux-stable-d927dea6392d5445a62f104baf8881ff5095d3ba.tar.gz linux-stable-d927dea6392d5445a62f104baf8881ff5095d3ba.tar.bz2 linux-stable-d927dea6392d5445a62f104baf8881ff5095d3ba.zip | |
block: don't warn when doing fsync on read-only devices
commit 8b2ded1c94c06f841f8c1612bcfa33c85012a36b upstream.
It is possible to call fsync on a read-only handle (for example, fsck.ext2
does it when doing read-only check), and this call results in kernel
warning.
The patch b089cfd95d32 ("block: don't warn for flush on read-only device")
attempted to disable the warning, but it is buggy and it doesn't
(op_is_flush tests flags, but bio_op strips off the flags).
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Fixes: 721c7fc701c7 ("block: fail op_is_write() requests to read-only partitions")
Cc: stable@vger.kernel.org # 4.18
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block')
| -rw-r--r-- | block/blk-core.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/block/blk-core.c b/block/blk-core.c index 746a5eac4541..cbaca5a73f2e 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -2161,9 +2161,12 @@ static inline bool bio_check_ro(struct bio *bio, struct hd_struct *part) { const int op = bio_op(bio); - if (part->policy && (op_is_write(op) && !op_is_flush(op))) { + if (part->policy && op_is_write(op)) { char b[BDEVNAME_SIZE]; + if (op_is_flush(bio->bi_opf) && !bio_sectors(bio)) + return false; + WARN_ONCE(1, "generic_make_request: Trying to write " "to read-only block-device %s (partno %d)\n", |