linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] direct-io: allow direct writes to empty inodes
Date: Fri, 26 Oct 2018 11:30:04 +0200	[thread overview]
Message-ID: <20181026093004.GA25227@quack2.suse.cz> (raw)
In-Reply-To: <20181008235823.5rpr4dqgriiacsvy@eaf>

On Mon 08-10-18 20:58:23, Ernesto A. Fern�ndez wrote:
> 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.
> 
> Signed-off-by: Ernesto A. Fern�ndez <ernesto.mnd.fernandez@gmail.com>

Good catch. The patch looks good. You can add:

Reviewed-by: Jan Kara <jack@suse.cz>

Also Jens often picks up patches for direct IO code so added him to CC.
Jens?

								Honza

> ---
>  fs/direct-io.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/direct-io.c b/fs/direct-io.c
> index 093fb54cd316..9a7b91a3b7a7 100644
> --- a/fs/direct-io.c
> +++ b/fs/direct-io.c
> @@ -679,6 +679,7 @@ static int get_more_blocks(struct dio *dio, struct dio_submit *sdio,
>  	unsigned long fs_count;	/* Number of filesystem-sized blocks */
>  	int create;
>  	unsigned int i_blkbits = sdio->blkbits + sdio->blkfactor;
> +	loff_t i_size;
>  
>  	/*
>  	 * If there was a memory error and we've overwritten all the
> @@ -708,8 +709,8 @@ static int get_more_blocks(struct dio *dio, struct dio_submit *sdio,
>  		 */
>  		create = dio->op == REQ_OP_WRITE;
>  		if (dio->flags & DIO_SKIP_HOLES) {
> -			if (fs_startblk <= ((i_size_read(dio->inode) - 1) >>
> -							i_blkbits))
> +			i_size = i_size_read(dio->inode);
> +			if (i_size && fs_startblk <= (i_size - 1) >> i_blkbits)
>  				create = 0;
>  		}
>  
> -- 
> 2.11.0
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2018-10-26 19:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 23:58 [PATCH] direct-io: allow direct writes to empty inodes Ernesto A. Fernández
2018-10-26  9:30 ` Jan Kara [this message]
2018-10-26 14:29   ` Jens Axboe
2018-10-27  4:12     ` Ernesto A. Fernández
2018-10-27 16:54       ` Jens Axboe
2019-01-07 18:03         ` Ernesto A. Fernández
2019-01-22  0:04           ` Ernesto A. Fernández
2019-01-22 15:27             ` Jens Axboe

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=20181026093004.GA25227@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=axboe@kernel.dk \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).