mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Jingbo Xu <jefflexu@linux.alibaba.com>,
	xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
	linux-erofs@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] erofs: avoid hardcoded blocksize for subpage block support
Date: Mon, 13 Mar 2023 20:07:32 +0800	[thread overview]
Message-ID: <691acb44-aaa6-10a8-4b03-d2a3b68421e5@linux.alibaba.com> (raw)
In-Reply-To: <20230306100200.117684-2-jefflexu@linux.alibaba.com>



On 2023/3/6 18:01, Jingbo Xu wrote:
> As the first step of converting hardcoded blocksize to that specified in
> on-disk superblock, convert all call sites of hardcoded blocksize to
> sb->s_blocksize except for:
> 
> 1) use sbi->blkszbits instead of sb->s_blocksize in
> erofs_superblock_csum_verify() since sb->s_blocksize has not been
> updated with the on-disk blocksize yet when the function is called.
> 
> 2) use inode->i_blkbits instead of sb->s_blocksize in erofs_bread(),
> since the inode operated on may be an anonymous inode in fscache mode.
> Currently the anonymous inode is allocated from an anonymous mount
> maintained in erofs, while in the near future we may allocate anonymous
> inodes from a generic API directly and thus have no access to the
> anonymous inode's i_sb.  Thus we keep the block size in i_blkbits for
> anonymous inodes in fscache mode.
> 
> Be noted that this patch only gets rid of the hardcoded blocksize, in
> preparation for actually setting the on-disk block size in the following
> patch.  The hard limit of constraining the block size to PAGE_SIZE still
> exists until the next patch.
> 
> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---

...

>   static int erofs_superblock_csum_verify(struct super_block *sb, void *sbdata)
>   {
> +	size_t len = (1 << EROFS_SB(sb)->blkszbits) - EROFS_SUPER_OFFSET;


Here len could be < 0, I think we could calculate crc32 as below:

	size_t len = 1 << EROFS_SB(sb)->blkszbits;

...

	if (len > EROFS_SUPER_OFFSET)             (>= 2k)
		len -= EROFS_SUPER_OFFSET;

Thanks,
Gao Xiang

  reply	other threads:[~2023-03-13 12:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 10:01 [PATCH v5 0/2] erofs: set block size to the on-disk block size Jingbo Xu
2023-03-06 10:01 ` [PATCH v5 1/2] erofs: avoid hardcoded blocksize for subpage block support Jingbo Xu
2023-03-13 12:07   ` Gao Xiang [this message]
2023-03-06 10:02 ` [PATCH v5 2/2] erofs: set block size to the on-disk block size Jingbo Xu
2023-03-13 12:04   ` Gao Xiang
2023-03-06 10:11 ` [PATCH v5 0/2] " Yue Hu

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=691acb44-aaa6-10a8-4b03-d2a3b68421e5@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiang@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

all inboxes | Powered by JetHome®