From: Al Viro <viro@zeniv.linux.org.uk>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 5/6] ocfs2: convert to use i_blockmask()
Date: Fri, 10 Mar 2023 03:26:11 +0000 [thread overview]
Message-ID: <20230310032611.GF3390869@ZenIV> (raw)
In-Reply-To: <20230309152127.41427-5-frank.li@vivo.com>
On Thu, Mar 09, 2023 at 11:21:26PM +0800, Yangtao Li wrote:
> Use i_blockmask() to simplify code. BTW convert ocfs2_is_io_unaligned
> to return bool type.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> v3:
> -none
> fs/ocfs2/file.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
> index efb09de4343d..baefab3b12c9 100644
> --- a/fs/ocfs2/file.c
> +++ b/fs/ocfs2/file.c
> @@ -2159,14 +2159,14 @@ int ocfs2_check_range_for_refcount(struct inode *inode, loff_t pos,
> return ret;
> }
>
> -static int ocfs2_is_io_unaligned(struct inode *inode, size_t count, loff_t pos)
> +static bool ocfs2_is_io_unaligned(struct inode *inode, size_t count, loff_t pos)
> {
> - int blockmask = inode->i_sb->s_blocksize - 1;
> + int blockmask = i_blockmask(inode);
> loff_t final_size = pos + count;
>
> if ((pos & blockmask) || (final_size & blockmask))
> - return 1;
> - return 0;
> + return true;
> + return false;
> }
Ugh...
return (pos | count) & blockmask;
surely? Conversion to bool will take care of the rest. Or you could make
that
return ((pos | count) & blockmask) != 0;
And the fact that the value will be the same (i.e. that ->i_blkbits is never
changed by ocfs2) is worth mentioning in commit message...
next prev parent reply other threads:[~2023-03-10 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 15:21 [Cluster-devel] [PATCH v3 1/6] fs: add i_blockmask() Yangtao Li
2023-03-09 15:21 ` [Cluster-devel] [PATCH v3 2/6] erofs: convert to use i_blockmask() Yangtao Li
2023-03-10 3:15 ` Al Viro
2023-03-10 3:42 ` Gao Xiang
2023-03-10 3:47 ` Gao Xiang
2023-03-10 3:51 ` [Cluster-devel] " Yangtao Li
2023-03-10 4:05 ` Al Viro
2023-03-10 6:50 ` Yangtao Li
2023-03-09 15:21 ` [Cluster-devel] [PATCH v3 3/6] gfs2: " Yangtao Li
2023-03-09 15:21 ` [Cluster-devel] [PATCH v3 4/6] ext4: " Yangtao Li
2023-03-10 3:19 ` Al Viro
2023-03-10 3:32 ` Al Viro
2023-03-09 15:21 ` [Cluster-devel] [PATCH v3 5/6] ocfs2: " Yangtao Li
2023-03-10 3:26 ` Al Viro [this message]
2023-03-09 15:21 ` [Cluster-devel] [PATCH v3 6/6] fs/remap_range: " Yangtao Li
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=20230310032611.GF3390869@ZenIV \
--to=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).