From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 3/4] xfs: convert open coded corruption check to use XFS_IS_CORRUPT
Date: Thu, 7 Nov 2019 10:25:42 -0800 [thread overview]
Message-ID: <20191107182542.GC2682@infradead.org> (raw)
In-Reply-To: <157309572922.45542.2780240623887540291.stgit@magnolia>
> bp = xfs_btree_get_bufs(tp->t_mountp, tp, agno, agbno);
> - if (!bp) {
> - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, tp->t_mountp);
> + if (XFS_IS_CORRUPT(tp->t_mountp, !bp)) {
> return -EFSCORRUPTED;
> }
We can kill the braces here now. Same for various other spots later
down.
> + if (XFS_IS_CORRUPT(mp,
> + ir.loaded != XFS_IFORK_NEXTENTS(ip, whichfork))) {
Somewhat strange indentation here.
> ASSERT(map && *map);
> @@ -2566,14 +2551,16 @@ xfs_dabuf_map(
> nirecs = 1;
> }
>
> - if (!xfs_da_map_covers_blocks(nirecs, irecs, bno, nfsb)) {
> - /* Caller ok with no mapping. */
> - if (mappedbno == -2) {
> - error = -1;
> - goto out;
> - }
> + covers_blocks = xfs_da_map_covers_blocks(nirecs, irecs, bno, nfsb);
> +
> + /* Caller ok with no mapping. */
> + if (mappedbno == -2 && !covers_blocks) {
> + error = -1;
> + goto out;
> + }
>
> - /* Caller expected a mapping, so abort. */
> + /* Caller expected a mapping, so abort. */
> + if (XFS_IS_CORRUPT(mp, !covers_blocks)) {
Why the restructure here?
This could have just become:
if (!XFS_IS_CORRUPT(mp != -2)) {
error = -1;
goto out;
}
not that I really like the current structure, but that change seems bit
out of place in these semi-mechanical fixups, and once we touch the
structure of this function and its callers there is so much more to
fix..
> index 7b845c052fb4..e1b9de6c7437 100644
> --- a/fs/xfs/libxfs/xfs_inode_fork.h
> +++ b/fs/xfs/libxfs/xfs_inode_fork.h
> @@ -87,6 +87,10 @@ struct xfs_ifork {
> #define XFS_IFORK_MAXEXT(ip, w) \
> (XFS_IFORK_SIZE(ip, w) / sizeof(xfs_bmbt_rec_t))
>
> +#define XFS_IFORK_MAPS_BLOCKS(ip, w) \
> + (XFS_IFORK_FORMAT((ip), (w)) == XFS_DINODE_FMT_EXTENTS || \
> + XFS_IFORK_FORMAT((ip), (w)) == XFS_DINODE_FMT_BTREE)
Why the double indentation? Also maybe XFS_IFORK_FORMAT_MAPS_BLOCKS
is a better name? Or maybe even turn it into an inline function with
a less shouting name? Also the addition of this helper is probably
worth being split into a separate patch.
> + head_block >= tail_block || head_cycle != (tail_cycle + 1)))
no need for the inner most braces here if you touch the line anyway.
next prev parent reply other threads:[~2019-11-07 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 3:01 [PATCH 0/4] xfs: refactor corruption checking and reporting Darrick J. Wong
2019-11-07 3:01 ` [PATCH 1/4] xfs: add a XFS_IS_CORRUPT macro Darrick J. Wong
2019-11-07 18:16 ` Christoph Hellwig
2019-11-07 3:02 ` [PATCH 2/4] xfs: kill the XFS_WANT_CORRUPT_* macros Darrick J. Wong
2019-11-07 18:16 ` Christoph Hellwig
2019-11-07 3:02 ` [PATCH 3/4] xfs: convert open coded corruption check to use XFS_IS_CORRUPT Darrick J. Wong
2019-11-07 18:25 ` Christoph Hellwig [this message]
2019-11-07 20:57 ` Darrick J. Wong
2019-11-08 0:01 ` Darrick J. Wong
2019-11-07 3:02 ` [PATCH 4/4] xfs: convert EIO to EFSCORRUPTED when log contents are invalid Darrick J. Wong
2019-11-07 8:46 ` Christoph Hellwig
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=20191107182542.GC2682@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.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;
as well as URLs for NNTP newsgroup(s).