From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 5/7] xfs: introduce a per-ag inode iterator
Date: Wed, 03 Jun 2009 17:01:13 -0500 [thread overview]
Message-ID: <4A26F2A9.8050300@sandeen.net> (raw)
In-Reply-To: <20090514171558.869514000@bombadil.infradead.org>
Christoph Hellwig wrote:
> From: Dave Chinner <david@fromorbit.com>
>
> Given that we walk across the per-ag inode lists so often, it makes sense to
> introduce an iterator for this.
>
> Convert the sync and reclaim code to use this new iterator, quota code will
> follow in the next patch.
>
> [hch: merged the lookup and execute callbacks back into one to get the
> pag_ici_lock locking correct and simplify the code flow]
>
> Signed-off-by: Dave Chinner <david@fromorbit.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Somehow I'm finding this hard to review, but...
> Index: xfs/fs/xfs/linux-2.6/xfs_sync.c
> ===================================================================
> --- xfs.orig/fs/xfs/linux-2.6/xfs_sync.c 2009-05-14 16:20:37.012658983 +0200
> +++ xfs/fs/xfs/linux-2.6/xfs_sync.c 2009-05-14 16:22:26.321659103 +0200
...
> +STATIC int
> +xfs_inode_ag_walk(
> + struct xfs_mount *mp,
> + xfs_agnumber_t ag,
> + int (*execute)(struct xfs_inode *ip,
> + struct xfs_perag *pag, int flags),
> + int flags,
> + int tag)
> +{
> + struct xfs_perag *pag = &mp->m_perag[ag];
> + uint32_t first_index;
> + int last_error = 0;
> + int skipped;
> +
> +restart:
> + skipped = 0;
> + first_index = 0;
> + do {
> + int error = 0;
> + xfs_inode_t *ip;
> +
> + ip = xfs_inode_ag_lookup(mp, pag, &first_index, tag);
> + if (!ip)
> + break;
> +
> + error = execute(ip, pag, flags);
> + if (error == EAGAIN) {
> + skipped++;
> + continue;
> + }
> + if (error)
> + last_error = error;
> + /*
> + * bail out if the filesystem is corrupted.
> + */
> + if (error == EFSCORRUPTED)
> + break;
Ok so here we are looking for EFSCORRUPTED from the "execute" function.
This might be xfs_sync_inode_data, xfs_sync_inode_attr, or
xfs_reclaim_inode_now. But ...
> +
> + } while (1);
...
> @@ -85,12 +201,17 @@ xfs_sync_inode_valid(
> STATIC int
> xfs_sync_inode_data(
> struct xfs_inode *ip,
> + struct xfs_perag *pag,
> int flags)
> {
> struct inode *inode = VFS_I(ip);
> struct address_space *mapping = inode->i_mapping;
> int error = 0;
>
> + error = xfs_sync_inode_valid(ip, pag);
> + if (error)
> + return 0;xfs_sync_inode_attr(
> +
xfs_sync_inode_valid can return 0, ENOENT, or EFSCORRUPTED.
Aren't we losing the error here...
> if (mapping_tagged(mapping, PAGECACHE_TAG_DIRTY)) {
> if (!xfs_ilock_nowait(ip, XFS_IOLOCK_SHARED)) {
> if (flags & SYNC_TRYLOCK)
> @@ -106,16 +227,22 @@ xfs_sync_inode_data(
> out_wait:
> if (flags & SYNC_IOWAIT)
> xfs_ioend_wait(ip);
> + IRELE(ip);
> return error;
> }
>
> STATIC int
> xfs_sync_inode_attr(
> struct xfs_inode *ip,
> + struct xfs_perag *pag,
> int flags)
> {
> int error = 0;
>
> + error = xfs_sync_inode_valid(ip, pag);
> + if (error)
> + return 0;
and here?
so xfs_sync_inode_data / xfs_sync_inode_attr are the "execute" in
xfs_inode_ag_walk():
> + error = execute(ip, pag, flags);
> + if (error == EAGAIN) {
> + skipped++;
> + continue;
> + }
> + if (error)
> + last_error = error;
above, and I think they're ignoring the return from
xfs_sync_inode_valid(), therefore xfs_inode_ag_walk won't see
EFSCORRUPTED from it either ... right?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-03 22:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 17:12 [PATCH 0/7] inode sync refactoring Christoph Hellwig
2009-05-14 17:12 ` [PATCH 1/7] xfs: split inode data writeback from xfs_sync_inodes_ag Christoph Hellwig
2009-05-15 4:49 ` Sujit Karataparambil
2009-05-15 17:21 ` Christoph Hellwig
2009-05-18 6:58 ` Dave Chinner
2009-05-26 20:14 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 2/7] xfs: split inode flushing " Christoph Hellwig
2009-05-15 4:52 ` Sujit Karataparambil
2009-05-15 17:22 ` Christoph Hellwig
2009-05-26 20:45 ` Eric Sandeen
2009-05-27 10:58 ` Christoph Hellwig
2009-05-27 20:11 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 3/7] xfs: factor out inode validation for sync Christoph Hellwig
2009-05-27 20:38 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 4/7] xfs: remove unused parameter from xfs_reclaim_inodes Christoph Hellwig
2009-05-27 20:44 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 5/7] xfs: introduce a per-ag inode iterator Christoph Hellwig
2009-06-03 22:01 ` Eric Sandeen [this message]
2009-06-04 11:00 ` Christoph Hellwig
2009-06-03 22:18 ` Eric Sandeen
2009-06-04 17:17 ` Christoph Hellwig
2009-06-05 18:18 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 6/7] xfs: use generic inode iterator in xfs_qm_dqrele_all_inodes Christoph Hellwig
2009-06-03 23:29 ` Josef 'Jeff' Sipek
2009-06-05 19:15 ` Eric Sandeen
2009-06-05 19:17 ` Christoph Hellwig
2009-06-05 20:11 ` Eric Sandeen
2009-05-14 17:12 ` [PATCH 7/7] xfs: split xfs_sync_inodes Christoph Hellwig
2009-06-03 23:26 ` Josef 'Jeff' Sipek
2009-06-04 10:45 ` Christoph Hellwig
2009-06-05 20:32 ` Eric Sandeen
2009-05-28 12:19 ` [PATCH 8/7] xfs: remove SYNC_IOWAIT Christoph Hellwig
2009-06-03 23:30 ` Josef 'Jeff' Sipek
2009-06-04 10:46 ` Christoph Hellwig
2009-06-05 20:37 ` Eric Sandeen
2009-05-28 12:19 ` [PATCH 9/7] xfs: remove SYNC_BDFLUSH Christoph Hellwig
2009-05-29 13:19 ` Sujit Karataparambil
2009-05-29 20:10 ` Christoph Hellwig
2009-05-30 8:27 ` Sujit Karataparambil
2009-06-05 20:45 ` Eric Sandeen
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=4A26F2A9.8050300@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.