From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3 07/13] xfs: check if an inode is cached and allocated
Date: Mon, 19 Jun 2017 08:07:08 -0400 [thread overview]
Message-ID: <20170619120708.GA25516@bfoster.bfoster> (raw)
In-Reply-To: <20170616175932.GF5421@birch.djwong.org>
On Fri, Jun 16, 2017 at 10:59:32AM -0700, Darrick J. Wong wrote:
> Check the inode cache for a particular inode number. If it's in the
> cache, check that it's not currently being reclaimed. If it's not being
> reclaimed, return zero if the inode is allocated. This function will be
> used by various scrubbers to decide if the cache is more up to date
> than the disk in terms of checking if an inode is allocated.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> v3: plumb in an opportunistic "get it from the cache" flag to _iget
> and refactor the helper to use it.
> ---
> fs/xfs/xfs_icache.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++--
> fs/xfs/xfs_icache.h | 4 ++++
> 2 files changed, 54 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c
> index f61c84f8..45845b7 100644
> --- a/fs/xfs/xfs_icache.c
> +++ b/fs/xfs/xfs_icache.c
> @@ -369,6 +369,11 @@ xfs_iget_cache_hit(
> if (ip->i_flags & XFS_IRECLAIMABLE) {
> trace_xfs_iget_reclaim(ip);
>
> + if (flags & XFS_IGET_INCORE) {
> + error = -EAGAIN;
> + goto out_error;
> + }
> +
> /*
> * We need to set XFS_IRECLAIM to prevent xfs_reclaim_inode
> * from stomping over us while we recycle the inode. We can't
> @@ -433,7 +438,8 @@ xfs_iget_cache_hit(
> if (lock_flags != 0)
> xfs_ilock(ip, lock_flags);
>
> - xfs_iflags_clear(ip, XFS_ISTALE | XFS_IDONTCACHE);
> + if (!(flags & XFS_IGET_INCORE))
> + xfs_iflags_clear(ip, XFS_ISTALE | XFS_IDONTCACHE);
> XFS_STATS_INC(mp, xs_ig_found);
>
> return 0;
> @@ -604,6 +610,10 @@ xfs_iget(
It might be a good idea to check (or assert) that _IGET_INCORE isn't
specified with any other flags that don't make sense. Otherwise this
looks good to me, thanks...
Reviewed-by: Brian Foster <bfoster@redhat.com>
> goto out_error_or_again;
> } else {
> rcu_read_unlock();
> + if (flags & XFS_IGET_INCORE) {
> + error = -ENOENT;
> + goto out_error_or_again;
> + }
> XFS_STATS_INC(mp, xs_ig_missed);
>
> error = xfs_iget_cache_miss(mp, pag, tp, ino, &ip,
> @@ -624,7 +634,7 @@ xfs_iget(
> return 0;
>
> out_error_or_again:
> - if (error == -EAGAIN) {
> + if (!(flags & XFS_IGET_INCORE) && error == -EAGAIN) {
> delay(1);
> goto again;
> }
> @@ -633,6 +643,44 @@ xfs_iget(
> }
>
> /*
> + * "Is this a cached inode that's also allocated?"
> + *
> + * Look up an inode by number in the given file system. If the inode is
> + * in cache and isn't in purgatory, return 1 if the inode is allocated
> + * and 0 if it is not. For all other cases (not in cache, being torn
> + * down, etc.), return a negative error code.
> + *
> + * The caller has to prevent inode allocation and freeing activity,
> + * presumably by locking the AGI buffer. This is to ensure that an
> + * inode cannot transition from allocated to freed until the caller is
> + * ready to allow that. If the inode is in an intermediate state (new,
> + * reclaimable, or being reclaimed), -EAGAIN will be returned; if the
> + * inode is not in the cache, -ENOENT will be returned. The caller must
> + * deal with these scenarios appropriately.
> + *
> + * This is a specialized use case for the online scrubber; if you're
> + * reading this, you probably want xfs_iget.
> + */
> +int
> +xfs_icache_inode_is_allocated(
> + struct xfs_mount *mp,
> + struct xfs_trans *tp,
> + xfs_ino_t ino,
> + bool *inuse)
> +{
> + struct xfs_inode *ip;
> + int error;
> +
> + error = xfs_iget(mp, tp, ino, XFS_IGET_INCORE, 0, &ip);
> + if (error)
> + return error;
> +
> + *inuse = !!(VFS_I(ip)->i_mode);
> + IRELE(ip);
> + return 0;
> +}
> +
> +/*
> * The inode lookup is done in batches to keep the amount of lock traffic and
> * radix tree lookups to a minimum. The batch size is a trade off between
> * lookup reduction and stack usage. This is in the reclaim path, so we can't
> diff --git a/fs/xfs/xfs_icache.h b/fs/xfs/xfs_icache.h
> index 9183f77..bff4d85 100644
> --- a/fs/xfs/xfs_icache.h
> +++ b/fs/xfs/xfs_icache.h
> @@ -47,6 +47,7 @@ struct xfs_eofblocks {
> #define XFS_IGET_CREATE 0x1
> #define XFS_IGET_UNTRUSTED 0x2
> #define XFS_IGET_DONTCACHE 0x4
> +#define XFS_IGET_INCORE 0x8 /* don't read from disk or reinit */
>
> /*
> * flags for AG inode iterator
> @@ -126,4 +127,7 @@ xfs_fs_eofblocks_from_user(
> return 0;
> }
>
> +int xfs_icache_inode_is_allocated(struct xfs_mount *mp, struct xfs_trans *tp,
> + xfs_ino_t ino, bool *inuse);
> +
> #endif
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-19 12:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 21:24 [PATCH v7 00/13] xfs: preparing for online scrub support Darrick J. Wong
2017-06-02 21:24 ` [PATCH 01/13] xfs: optimize _btree_query_all Darrick J. Wong
2017-06-06 13:32 ` Brian Foster
2017-06-06 17:43 ` Darrick J. Wong
2017-06-07 1:18 ` [PATCH v2 " Darrick J. Wong
2017-06-07 14:22 ` Brian Foster
2017-06-02 21:24 ` [PATCH 02/13] xfs: remove double-underscore integer types Darrick J. Wong
2017-06-02 21:24 ` [PATCH 03/13] xfs: always compile the btree inorder check functions Darrick J. Wong
2017-06-06 13:32 ` Brian Foster
2017-06-02 21:24 ` [PATCH 04/13] xfs: export various function for the online scrubber Darrick J. Wong
2017-06-06 13:32 ` Brian Foster
2017-06-02 21:24 ` [PATCH 05/13] xfs: plumb in needed functions for range querying of various btrees Darrick J. Wong
2017-06-06 13:33 ` Brian Foster
2017-06-02 21:24 ` [PATCH 06/13] xfs: export _inobt_btrec_to_irec and _ialloc_cluster_alignment for scrub Darrick J. Wong
2017-06-06 16:27 ` Brian Foster
2017-06-06 17:46 ` Darrick J. Wong
2017-06-02 21:24 ` [PATCH 07/13] xfs: check if an inode is cached and allocated Darrick J. Wong
2017-06-06 16:28 ` Brian Foster
2017-06-06 18:40 ` Darrick J. Wong
2017-06-07 14:22 ` Brian Foster
2017-06-15 5:00 ` Darrick J. Wong
2017-06-07 1:21 ` [PATCH v2 " Darrick J. Wong
2017-06-16 17:59 ` [PATCH v3 " Darrick J. Wong
2017-06-19 12:07 ` Brian Foster [this message]
2017-06-02 21:24 ` [PATCH 08/13] xfs: reflink find shared should take a transaction Darrick J. Wong
2017-06-06 16:28 ` Brian Foster
2017-06-02 21:24 ` [PATCH 09/13] xfs: separate function to check if reflink flag needed Darrick J. Wong
2017-06-06 16:28 ` Brian Foster
2017-06-06 18:05 ` Darrick J. Wong
2017-06-07 1:26 ` [PATCH v2 " Darrick J. Wong
2017-06-07 14:22 ` Brian Foster
2017-06-02 21:25 ` [PATCH 10/13] xfs: refactor the ifork block counting function Darrick J. Wong
2017-06-06 16:29 ` Brian Foster
2017-06-06 18:51 ` Darrick J. Wong
2017-06-06 20:35 ` Darrick J. Wong
2017-06-07 1:29 ` [PATCH v2 9.9/13] xfs: make _bmap_count_blocks consistent wrt delalloc extent behavior Darrick J. Wong
2017-06-07 15:11 ` Brian Foster
2017-06-07 16:19 ` Darrick J. Wong
2017-06-07 1:29 ` [PATCH v2 10/13] xfs: refactor the ifork block counting function Darrick J. Wong
2017-06-07 15:11 ` Brian Foster
2017-06-02 21:25 ` [PATCH 11/13] xfs: return the hash value of a leaf1 directory block Darrick J. Wong
2017-06-08 13:02 ` Brian Foster
2017-06-08 15:53 ` Darrick J. Wong
2017-06-08 16:31 ` Brian Foster
2017-06-08 16:43 ` Darrick J. Wong
2017-06-08 16:52 ` Brian Foster
2017-06-08 18:22 ` [PATCH v2 " Darrick J. Wong
2017-06-09 12:54 ` Brian Foster
2017-06-02 21:25 ` [PATCH 12/13] xfs: pass along transaction context when reading directory block buffers Darrick J. Wong
2017-06-08 13:02 ` Brian Foster
2017-06-02 21:25 ` [PATCH 13/13] xfs: pass along transaction context when reading xattr " Darrick J. Wong
2017-06-08 13:02 ` Brian Foster
2017-06-02 22:19 ` [PATCH 14/13] xfs: allow reading of already-locked remote symbolic link Darrick J. Wong
2017-06-08 13:02 ` Brian Foster
2017-06-26 6:04 ` [PATCH 15/13] xfs: grab dquots without taking the ilock Darrick J. Wong
2017-06-27 11:00 ` 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=20170619120708.GA25516@bfoster.bfoster \
--to=bfoster@redhat.com \
--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).