From: Brian Foster <bfoster@redhat.com>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: linux-xfs@vger.kernel.org, "Darrick J . Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH v2 2/2] xfs: clean up calculation of LR header blocks
Date: Fri, 4 Sep 2020 07:25:48 -0400 [thread overview]
Message-ID: <20200904112548.GC529978@bfoster> (raw)
In-Reply-To: <20200904082516.31205-3-hsiangkao@redhat.com>
On Fri, Sep 04, 2020 at 04:25:16PM +0800, Gao Xiang wrote:
> Let's use DIV_ROUND_UP() to calculate log record header
> blocks as what did in xlog_get_iclog_buffer_size() and
> wrap up common helpers for log recovery.
>
> Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> ---
> v1: https://lore.kernel.org/r/20200902140923.24392-1-hsiangkao@redhat.com
>
> changes since v1:
> - add another helper xlog_logrec_hblks() for the cases with
> xfs_sb_version_haslogv2(), and use xlog_logrecv2_hblks()
> for the case of xlog_do_recovery_pass() since it has more
> complex logic other than just calculate hblks...
>
> fs/xfs/xfs_log.c | 4 +--
> fs/xfs/xfs_log_recover.c | 53 ++++++++++++++++------------------------
> 2 files changed, 22 insertions(+), 35 deletions(-)
>
...
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index 28d952794bfa..c6163065f6e0 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -397,6 +397,23 @@ xlog_find_verify_cycle(
> return error;
> }
>
> +static inline int xlog_logrecv2_hblks(struct xlog_rec_header *rh)
> +{
> + int h_size = be32_to_cpu(rh->h_size);
> +
> + if ((be32_to_cpu(rh->h_version) & XLOG_VERSION_2) &&
> + h_size > XLOG_HEADER_CYCLE_SIZE)
> + return DIV_ROUND_UP(h_size, XLOG_HEADER_CYCLE_SIZE);
> + return 1;
> +}
> +
> +static inline int xlog_logrec_hblks(struct xlog *log, xlog_rec_header_t *rh)
> +{
> + if (!xfs_sb_version_haslogv2(&log->l_mp->m_sb))
> + return 1;
> + return xlog_logrecv2_hblks(rh);
> +}
> +
h_version is assigned based on xfs_sb_version_haslogv2() in the first
place so I'm not sure I see the need for multiple helpers like this, at
least with the current code. I can't really speak to why some code
checks the feature bit and/or the record header version and not the
other way around, but perhaps there's some historical reason I'm not
aware of. Regardless, is there ever a case where
xfs_sb_version_haslogv2() == true and h_version != 2? That strikes me as
more of a corruption scenario than anything..
Brian
> /*
> * Potentially backup over partial log record write.
> *
> @@ -489,15 +506,7 @@ xlog_find_verify_log_record(
> * reset last_blk. Only when last_blk points in the middle of a log
> * record do we update last_blk.
> */
> - if (xfs_sb_version_haslogv2(&log->l_mp->m_sb)) {
> - uint h_size = be32_to_cpu(head->h_size);
> -
> - xhdrs = h_size / XLOG_HEADER_CYCLE_SIZE;
> - if (h_size % XLOG_HEADER_CYCLE_SIZE)
> - xhdrs++;
> - } else {
> - xhdrs = 1;
> - }
> + xhdrs = xlog_logrec_hblks(log, head);
>
> if (*last_blk - i + extra_bblks !=
> BTOBB(be32_to_cpu(head->h_len)) + xhdrs)
> @@ -1184,22 +1193,7 @@ xlog_check_unmount_rec(
> * below. We won't want to clear the unmount record if there is one, so
> * we pass the lsn of the unmount record rather than the block after it.
> */
> - if (xfs_sb_version_haslogv2(&log->l_mp->m_sb)) {
> - int h_size = be32_to_cpu(rhead->h_size);
> - int h_version = be32_to_cpu(rhead->h_version);
> -
> - if ((h_version & XLOG_VERSION_2) &&
> - (h_size > XLOG_HEADER_CYCLE_SIZE)) {
> - hblks = h_size / XLOG_HEADER_CYCLE_SIZE;
> - if (h_size % XLOG_HEADER_CYCLE_SIZE)
> - hblks++;
> - } else {
> - hblks = 1;
> - }
> - } else {
> - hblks = 1;
> - }
> -
> + hblks = xlog_logrec_hblks(log, rhead);
> after_umount_blk = xlog_wrap_logbno(log,
> rhead_blk + hblks + BTOBB(be32_to_cpu(rhead->h_len)));
>
> @@ -3024,15 +3018,10 @@ xlog_do_recovery_pass(
> if (error)
> goto bread_err1;
>
> - if ((be32_to_cpu(rhead->h_version) & XLOG_VERSION_2) &&
> - (h_size > XLOG_HEADER_CYCLE_SIZE)) {
> - hblks = h_size / XLOG_HEADER_CYCLE_SIZE;
> - if (h_size % XLOG_HEADER_CYCLE_SIZE)
> - hblks++;
> + hblks = xlog_logrecv2_hblks(rhead);
> + if (hblks != 1) {
> kmem_free(hbp);
> hbp = xlog_alloc_buffer(log, hblks);
> - } else {
> - hblks = 1;
> }
> } else {
> ASSERT(log->l_sectBBsize == 1);
> --
> 2.18.1
>
next prev parent reply other threads:[~2020-09-04 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 8:25 [PATCH 0/2] xfs: random patches on log recovery Gao Xiang
2020-09-04 8:25 ` [PATCH v3 1/2] xfs: avoid LR buffer overrun due to crafted h_{len,size} Gao Xiang
2020-09-04 11:25 ` Brian Foster
2020-09-04 12:46 ` Gao Xiang
2020-09-04 13:37 ` Brian Foster
2020-09-04 15:01 ` Gao Xiang
2020-09-04 16:31 ` Brian Foster
2020-09-04 8:25 ` [PATCH v2 2/2] xfs: clean up calculation of LR header blocks Gao Xiang
2020-09-04 11:25 ` Brian Foster [this message]
2020-09-04 12:59 ` Gao Xiang
2020-09-04 13:37 ` Brian Foster
2020-09-04 15:07 ` Gao Xiang
2020-09-04 16:32 ` Brian Foster
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=20200904112548.GC529978@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hsiangkao@redhat.com \
--cc=linux-xfs@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