direct-io: allow direct writes to empty inodes
authorErnesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
Mon, 8 Oct 2018 23:58:23 +0000 (20:58 -0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 5 Mar 2019 16:57:05 +0000 (17:57 +0100)
commit93ab28b29c5719486056b4d1bddadd22be4286fa
tree4a9190d6ee19c2df7c287c396ed11d0128c3e7d7
parent2b7d22eb15d1052de3047c4a4f89df93410a155b
direct-io: allow direct writes to empty inodes

[ Upstream commit 8b9433eb4de3c26a9226c981c283f9f4896ae030 ]

On a DIO_SKIP_HOLES filesystem, the ->get_block() method is currently
not allowed to create blocks for an empty inode.  This confusion comes
from trying to bit shift a negative number, so check the size of the
inode first.

The problem is most visible for hfsplus, because the fallback to
buffered I/O doesn't happen and the write fails with EIO.  This is in
part the fault of the module, because it gives a wrong return value on
->get_block(); that will be fixed in a separate patch.

Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/direct-io.c