From: Nikolay Borisov <nborisov@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH] direct-io: Minor cleanups in do_blockdev_direct_IO
Date: Sat, 3 Mar 2018 10:16:35 +0200 [thread overview]
Message-ID: <fcc65c30-c263-2a27-f7b0-7df6d047c21d@suse.com> (raw)
In-Reply-To: <20180302162400.f36d0d068bd0a08442536a2c@linux-foundation.org>
On 3.03.2018 02:24, Andrew Morton wrote:
> On Mon, 26 Feb 2018 11:54:30 +0200 Nikolay Borisov <nborisov@suse.com> wrote:
>
>> We already get the block counts and the calculate the end block at the
>> beginning of the function. Let's use the local variables for consistency and
>> readability. No functional changes
>>
>
> Fair enough.
>
>> --- a/fs/direct-io.c
>> +++ b/fs/direct-io.c
>> @@ -1200,7 +1200,7 @@ do_blockdev_direct_IO(struct kiocb *iocb, struct inode *inode,
>> }
>>
>> /* watch out for a 0 len io from a tricksy fs */
>> - if (iov_iter_rw(iter) == READ && !iov_iter_count(iter))
>> + if (iov_iter_rw(iter) == READ && !count)
>> return 0;
>>
>> dio = kmem_cache_alloc(dio_cache, GFP_KERNEL);
>> @@ -1316,8 +1316,7 @@ do_blockdev_direct_IO(struct kiocb *iocb, struct inode *inode,
>>
>> dio->should_dirty = (iter->type == ITER_IOVEC);
>> sdio.iter = iter;
>> - sdio.final_block_in_request =
>> - (offset + iov_iter_count(iter)) >> blkbits;
>> + sdio.final_block_in_request = end >> blkbits;
>>
>> /*
>> * In case of non-aligned buffers, we may need 2 more
>
> It's always scary to see a local being used in this fashion so far away
> from where it was initialized. However, we can get our warm fuzzy
> feelings by doing this:
>
Good point !
> --- a/fs/direct-io.c~direct-io-minor-cleanups-in-do_blockdev_direct_io-fix
> +++ a/fs/direct-io.c
> @@ -1178,9 +1178,9 @@ do_blockdev_direct_IO(struct kiocb *iocb
> unsigned blkbits = i_blkbits;
> unsigned blocksize_mask = (1 << blkbits) - 1;
> ssize_t retval = -EINVAL;
> - size_t count = iov_iter_count(iter);
> + const size_t count = iov_iter_count(iter);
> loff_t offset = iocb->ki_pos;
> - loff_t end = offset + count;
> + const loff_t end = offset + count;
> struct dio *dio;
> struct dio_submit sdio = { 0, };
> struct buffer_head map_bh = { 0, };
> _
I assume you don't want me to resend but will just fold the changes
yourself?
>
>
next prev parent reply other threads:[~2018-03-03 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 9:54 Nikolay Borisov
2018-03-03 0:24 ` Andrew Morton
2018-03-03 8:16 ` Nikolay Borisov [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 7:10 Nikolay Borisov
2017-08-03 14:08 ` Jeff Moyer
2017-09-15 19:34 ` Nikolay Borisov
2018-02-21 17:48 ` Nikolay Borisov
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=fcc65c30-c263-2a27-f7b0-7df6d047c21d@suse.com \
--to=nborisov@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®