From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Solve a problem of crossing the boundary in updating backups
Date: Tue, 6 Oct 2015 09:22:11 +0800 [thread overview]
Message-ID: <56132243.6050804@huawei.com> (raw)
In-Reply-To: <5611F380.2050102@huawei.com>
On 2015/10/5 11:50, jiangyiwen wrote:
> In update_backups func, it exists a problem of crossing the boundary
> as follows:
> we assume that lun will be resized to 1TB(cluster_size is 32kb),
> it will include 0~33554431 cluster, in update_backups func,
> it will backup super block in location of 1TB which is the 33554432th
> cluster, so the phenomenon of crossing the boundary is happened.
>
> Signed-off-by: Yiwen Jiang <jiangyiwen@huawei.com>
Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
> ---
> fs/ocfs2/resize.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/resize.c b/fs/ocfs2/resize.c
> index d5da6f6..10ad87b 100644
> --- a/fs/ocfs2/resize.c
> +++ b/fs/ocfs2/resize.c
> @@ -187,7 +187,7 @@ static int update_backups(struct inode * inode, u32 clusters, char *data)
> for (i = 0; i < OCFS2_MAX_BACKUP_SUPERBLOCKS; i++) {
> blkno = ocfs2_backup_super_blkno(inode->i_sb, i);
> cluster = ocfs2_blocks_to_clusters(inode->i_sb, blkno);
> - if (cluster > clusters)
> + if (cluster >= clusters)
> break;
>
> ret = ocfs2_read_blocks_sync(osb, blkno, 1, &backup);
>
prev parent reply other threads:[~2015-10-06 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 3:50 [Ocfs2-devel] [PATCH] ocfs2: Solve a problem of crossing the boundary in updating backups jiangyiwen
2015-10-06 1:22 ` Joseph Qi [this message]
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=56132243.6050804@huawei.com \
--to=joseph.qi@huawei.com \
--cc=ocfs2-devel@oss.oracle.com \
/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