From: Carlos Maiolino <cmaiolino@redhat.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: Fwd: [RESEND PATCH 2/2] ext4: ext4_inode_is_fast_symlink should use cluster size
Date: Mon, 23 Dec 2013 10:17:04 -0200 [thread overview]
Message-ID: <20131223121703.GA4284@orion.maiolino.org> (raw)
In-Reply-To: <CAGBYx2Zx7jnK-DmM7=RCCVwz4N0FfE_-=eETO8OkLt5McCXttg@mail.gmail.com>
On Fri, Dec 20, 2013 at 01:13:33PM +0800, Yongqiang Yang wrote:
> From: Yongqiang Yang <xiaoqiangnk@gmail.com>
>
> can be reproduced by xfstests 62 with bigalloc and 128bit size inode.
>
> Signed-off-by: Yongqiang Yang <yangyongqiang01@baidu.com>
> ---
> fs/ext4/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index 9115f28..1869fcf 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -145,7 +145,7 @@ static int ext4_meta_trans_blocks(struct inode
> *inode, int lblocks,
> static int ext4_inode_is_fast_symlink(struct inode *inode)
> {
> int ea_blocks = EXT4_I(inode)->i_file_acl ?
> - (inode->i_sb->s_blocksize >> 9) : 0;
> + EXT4_CLUSTER_SIZE(inode->i_sb) >> 9 : 0;
Code looks good, but looks like it has an extra TAB here. Just a cosmetic thing;
despite that, consider it
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
--
Carlos
next prev parent reply other threads:[~2013-12-23 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1387515880-10185-1-git-send-email-yangyongqiang01@baidu.com>
2013-12-20 5:11 ` Fwd: [RESEND PATCH 1/2] ext4: fix a typo in extents.c Yongqiang Yang
2013-12-20 5:11 ` Yongqiang Yang
2013-12-23 12:17 ` Carlos Maiolino
2014-01-06 14:52 ` Theodore Ts'o
[not found] ` <1387515880-10185-2-git-send-email-yangyongqiang01@baidu.com>
2013-12-20 5:13 ` Fwd: [RESEND PATCH 2/2] ext4: ext4_inode_is_fast_symlink should use cluster size Yongqiang Yang
2013-12-23 12:17 ` Carlos Maiolino [this message]
2013-12-23 19:33 ` Andreas Dilger
2014-01-06 14:51 ` Fwd: " Theodore Ts'o
2014-01-06 17:47 ` Andreas Dilger
2014-01-06 19:45 ` Theodore Ts'o
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=20131223121703.GA4284@orion.maiolino.org \
--to=cmaiolino@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).