From: Dave Chinner <david@fromorbit.com>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCHv2 5/5] xfs: kill off l_sectbb_mask
Date: Sat, 17 Apr 2010 11:34:54 +1000 [thread overview]
Message-ID: <20100417013454.GF2493@dastard> (raw)
In-Reply-To: <201004162054.o3GKs54f025204@stout.americas.sgi.com>
On Fri, Apr 16, 2010 at 03:54:05PM -0500, Alex Elder wrote:
> There remains only one user of the l_sectbb_mask field in the log
> structure. Just kill it off and compute the mask where needed from
> the power-of-2 sector size.
>
> (Only update from last post is to accomodate the changes in the
> previous patch in the series.)
>
> Signed-off-by: Alex Elder <aelder@sgi.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> xfs_buf_t *bp)
> {
> + xfs_daddr_t offset;
> xfs_caddr_t ptr;
>
> - if (log->l_sectBBsize == 1)
> - return XFS_BUF_PTR(bp);
> + offset = blk_no & ((xfs_daddr_t) log->l_sectBBsize - 1);
> + ptr = XFS_BUF_PTR(bp) + BBTOB(offset);
> +
> + ASSERT(ptr + BBTOB(nbblks) <= XFS_BUF_PTR(bp) + XFS_BUF_SIZE(bp));
The ASSERT is more obfuscated than it needs to be. It's not obvious
that it is bounds checking offset+nbblks. i.e. I prefer the original
format like:
ASSERT(BBTOB(offset + nbblks) <= XFS_BUF_SIZE(bp));
but otherwise it looks good. Anyway, minor nitpick, so:
Reviewed-by: Dave Chinner <david@fromorbit.com>
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-17 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 20:54 [PATCHv2 5/5] xfs: kill off l_sectbb_mask Alex Elder
2010-04-17 1:34 ` Dave Chinner [this message]
2010-04-18 17:21 ` Christoph Hellwig
2010-04-18 17:29 ` Christoph Hellwig
2010-04-19 13:53 ` Alex Elder
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=20100417013454.GF2493@dastard \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=xfs@oss.sgi.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