From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 4/4] xfs: add xfs_inode_free
Date: Thu, 06 Aug 2009 18:54:53 -0500 [thread overview]
Message-ID: <4A7B6D4D.8090707@sandeen.net> (raw)
In-Reply-To: <20090804141836.782959000@bombadil.infradead.org>
Christoph Hellwig wrote:
> When we want to tear down an inode that lost the add to the cache race
> in XFS we must not call into ->destroy_inode because that would delete
> the inode that won the race from the inode cache radix tree.
>
> This patch uses splits a new xfs_inode_free helper out of xfs_ireclaim
> and uses that plus __destroy_inode to make sure we really only free
> the memory allocted for the inode that lost the race, and not mess with
> the inode cache state.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
Looks right to me.
Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
> Index: linux-2.6/fs/xfs/xfs_iget.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_iget.c 2009-08-03 01:23:29.878784477 +0200
> +++ linux-2.6/fs/xfs/xfs_iget.c 2009-08-03 01:25:01.601784988 +0200
> @@ -116,6 +116,71 @@ xfs_inode_alloc(
> return ip;
> }
>
> +STATIC void
> +xfs_inode_free(
> + struct xfs_inode *ip)
> +{
> + switch (ip->i_d.di_mode & S_IFMT) {
> + case S_IFREG:
> + case S_IFDIR:
> + case S_IFLNK:
> + xfs_idestroy_fork(ip, XFS_DATA_FORK);
> + break;
> + }
> +
> + if (ip->i_afp)
> + xfs_idestroy_fork(ip, XFS_ATTR_FORK);
> +
> +#ifdef XFS_INODE_TRACE
> + ktrace_free(ip->i_trace);
> +#endif
> +#ifdef XFS_BMAP_TRACE
> + ktrace_free(ip->i_xtrace);
> +#endif
> +#ifdef XFS_BTREE_TRACE
> + ktrace_free(ip->i_btrace);
> +#endif
> +#ifdef XFS_RW_TRACE
> + ktrace_free(ip->i_rwtrace);
> +#endif
> +#ifdef XFS_ILOCK_TRACE
> + ktrace_free(ip->i_lock_trace);
> +#endif
> +#ifdef XFS_DIR2_TRACE
> + ktrace_free(ip->i_dir_trace);
> +#endif
> +
> + if (ip->i_itemp) {
> + /*
> + * Only if we are shutting down the fs will we see an
> + * inode still in the AIL. If it is there, we should remove
> + * it to prevent a use-after-free from occurring.
> + */
> + xfs_log_item_t *lip = &ip->i_itemp->ili_item;
> + struct xfs_ail *ailp = lip->li_ailp;
> +
> + ASSERT(((lip->li_flags & XFS_LI_IN_AIL) == 0) ||
> + XFS_FORCED_SHUTDOWN(ip->i_mount));
> + if (lip->li_flags & XFS_LI_IN_AIL) {
> + spin_lock(&ailp->xa_lock);
> + if (lip->li_flags & XFS_LI_IN_AIL)
> + xfs_trans_ail_delete(ailp, lip);
> + else
> + spin_unlock(&ailp->xa_lock);
> + }
> + xfs_inode_item_destroy(ip);
> + ip->i_itemp = NULL;
> + }
> +
> + /* asserts to verify all state is correct here */
> + ASSERT(atomic_read(&ip->i_iocount) == 0);
> + ASSERT(atomic_read(&ip->i_pincount) == 0);
> + ASSERT(!spin_is_locked(&ip->i_flags_lock));
> + ASSERT(completion_done(&ip->i_flush));
> +
> + kmem_zone_free(xfs_inode_zone, ip);
> +}
> +
> /*
> * Check the validity of the inode we just found it the cache
> */
> @@ -303,7 +368,8 @@ out_preload_end:
> if (lock_flags)
> xfs_iunlock(ip, lock_flags);
> out_destroy:
> - xfs_destroy_inode(ip);
> + __destroy_inode(VFS_I(ip));
> + xfs_inode_free(ip);
> return error;
> }
>
> @@ -506,62 +572,7 @@ xfs_ireclaim(
> xfs_qm_dqdetach(ip);
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
>
> - switch (ip->i_d.di_mode & S_IFMT) {
> - case S_IFREG:
> - case S_IFDIR:
> - case S_IFLNK:
> - xfs_idestroy_fork(ip, XFS_DATA_FORK);
> - break;
> - }
> -
> - if (ip->i_afp)
> - xfs_idestroy_fork(ip, XFS_ATTR_FORK);
> -
> -#ifdef XFS_INODE_TRACE
> - ktrace_free(ip->i_trace);
> -#endif
> -#ifdef XFS_BMAP_TRACE
> - ktrace_free(ip->i_xtrace);
> -#endif
> -#ifdef XFS_BTREE_TRACE
> - ktrace_free(ip->i_btrace);
> -#endif
> -#ifdef XFS_RW_TRACE
> - ktrace_free(ip->i_rwtrace);
> -#endif
> -#ifdef XFS_ILOCK_TRACE
> - ktrace_free(ip->i_lock_trace);
> -#endif
> -#ifdef XFS_DIR2_TRACE
> - ktrace_free(ip->i_dir_trace);
> -#endif
> - if (ip->i_itemp) {
> - /*
> - * Only if we are shutting down the fs will we see an
> - * inode still in the AIL. If it is there, we should remove
> - * it to prevent a use-after-free from occurring.
> - */
> - xfs_log_item_t *lip = &ip->i_itemp->ili_item;
> - struct xfs_ail *ailp = lip->li_ailp;
> -
> - ASSERT(((lip->li_flags & XFS_LI_IN_AIL) == 0) ||
> - XFS_FORCED_SHUTDOWN(ip->i_mount));
> - if (lip->li_flags & XFS_LI_IN_AIL) {
> - spin_lock(&ailp->xa_lock);
> - if (lip->li_flags & XFS_LI_IN_AIL)
> - xfs_trans_ail_delete(ailp, lip);
> - else
> - spin_unlock(&ailp->xa_lock);
> - }
> - xfs_inode_item_destroy(ip);
> - ip->i_itemp = NULL;
> - }
> - /* asserts to verify all state is correct here */
> - ASSERT(atomic_read(&ip->i_iocount) == 0);
> - ASSERT(atomic_read(&ip->i_pincount) == 0);
> - ASSERT(!spin_is_locked(&ip->i_flags_lock));
> - ASSERT(completion_done(&ip->i_flush));
> - kmem_zone_free(xfs_inode_zone, ip);
> + xfs_inode_free(ip);
> }
>
> /*
> Index: linux-2.6/fs/xfs/xfs_inode.h
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_inode.h 2009-08-03 01:23:39.876532108 +0200
> +++ linux-2.6/fs/xfs/xfs_inode.h 2009-08-03 01:23:47.411789594 +0200
> @@ -310,26 +310,6 @@ static inline struct inode *VFS_I(struct
> }
>
> /*
> - * Get rid of a partially initialized inode.
> - *
> - * We have to go through destroy_inode to make sure allocations
> - * from init_inode_always like the security data are undone.
> - *
> - * We mark the inode bad so that it takes the short cut in
> - * the reclaim path instead of going through the flush path
> - * which doesn't make sense for an inode that has never seen the
> - * light of day.
> - */
> -static inline void xfs_destroy_inode(struct xfs_inode *ip)
> -{
> - struct inode *inode = VFS_I(ip);
> -
> - make_bad_inode(inode);
> - __destroy_inode(inode);
> - inode->i_sb->s_op->destroy_inode(inode);
> -}
> -
> -/*
> * i_flags helper functions
> */
> static inline void
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs: add xfs_inode_free
Date: Thu, 06 Aug 2009 18:54:53 -0500 [thread overview]
Message-ID: <4A7B6D4D.8090707@sandeen.net> (raw)
In-Reply-To: <20090804141836.782959000@bombadil.infradead.org>
Christoph Hellwig wrote:
> When we want to tear down an inode that lost the add to the cache race
> in XFS we must not call into ->destroy_inode because that would delete
> the inode that won the race from the inode cache radix tree.
>
> This patch uses splits a new xfs_inode_free helper out of xfs_ireclaim
> and uses that plus __destroy_inode to make sure we really only free
> the memory allocted for the inode that lost the race, and not mess with
> the inode cache state.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
Looks right to me.
Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
> Index: linux-2.6/fs/xfs/xfs_iget.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_iget.c 2009-08-03 01:23:29.878784477 +0200
> +++ linux-2.6/fs/xfs/xfs_iget.c 2009-08-03 01:25:01.601784988 +0200
> @@ -116,6 +116,71 @@ xfs_inode_alloc(
> return ip;
> }
>
> +STATIC void
> +xfs_inode_free(
> + struct xfs_inode *ip)
> +{
> + switch (ip->i_d.di_mode & S_IFMT) {
> + case S_IFREG:
> + case S_IFDIR:
> + case S_IFLNK:
> + xfs_idestroy_fork(ip, XFS_DATA_FORK);
> + break;
> + }
> +
> + if (ip->i_afp)
> + xfs_idestroy_fork(ip, XFS_ATTR_FORK);
> +
> +#ifdef XFS_INODE_TRACE
> + ktrace_free(ip->i_trace);
> +#endif
> +#ifdef XFS_BMAP_TRACE
> + ktrace_free(ip->i_xtrace);
> +#endif
> +#ifdef XFS_BTREE_TRACE
> + ktrace_free(ip->i_btrace);
> +#endif
> +#ifdef XFS_RW_TRACE
> + ktrace_free(ip->i_rwtrace);
> +#endif
> +#ifdef XFS_ILOCK_TRACE
> + ktrace_free(ip->i_lock_trace);
> +#endif
> +#ifdef XFS_DIR2_TRACE
> + ktrace_free(ip->i_dir_trace);
> +#endif
> +
> + if (ip->i_itemp) {
> + /*
> + * Only if we are shutting down the fs will we see an
> + * inode still in the AIL. If it is there, we should remove
> + * it to prevent a use-after-free from occurring.
> + */
> + xfs_log_item_t *lip = &ip->i_itemp->ili_item;
> + struct xfs_ail *ailp = lip->li_ailp;
> +
> + ASSERT(((lip->li_flags & XFS_LI_IN_AIL) == 0) ||
> + XFS_FORCED_SHUTDOWN(ip->i_mount));
> + if (lip->li_flags & XFS_LI_IN_AIL) {
> + spin_lock(&ailp->xa_lock);
> + if (lip->li_flags & XFS_LI_IN_AIL)
> + xfs_trans_ail_delete(ailp, lip);
> + else
> + spin_unlock(&ailp->xa_lock);
> + }
> + xfs_inode_item_destroy(ip);
> + ip->i_itemp = NULL;
> + }
> +
> + /* asserts to verify all state is correct here */
> + ASSERT(atomic_read(&ip->i_iocount) == 0);
> + ASSERT(atomic_read(&ip->i_pincount) == 0);
> + ASSERT(!spin_is_locked(&ip->i_flags_lock));
> + ASSERT(completion_done(&ip->i_flush));
> +
> + kmem_zone_free(xfs_inode_zone, ip);
> +}
> +
> /*
> * Check the validity of the inode we just found it the cache
> */
> @@ -303,7 +368,8 @@ out_preload_end:
> if (lock_flags)
> xfs_iunlock(ip, lock_flags);
> out_destroy:
> - xfs_destroy_inode(ip);
> + __destroy_inode(VFS_I(ip));
> + xfs_inode_free(ip);
> return error;
> }
>
> @@ -506,62 +572,7 @@ xfs_ireclaim(
> xfs_qm_dqdetach(ip);
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
>
> - switch (ip->i_d.di_mode & S_IFMT) {
> - case S_IFREG:
> - case S_IFDIR:
> - case S_IFLNK:
> - xfs_idestroy_fork(ip, XFS_DATA_FORK);
> - break;
> - }
> -
> - if (ip->i_afp)
> - xfs_idestroy_fork(ip, XFS_ATTR_FORK);
> -
> -#ifdef XFS_INODE_TRACE
> - ktrace_free(ip->i_trace);
> -#endif
> -#ifdef XFS_BMAP_TRACE
> - ktrace_free(ip->i_xtrace);
> -#endif
> -#ifdef XFS_BTREE_TRACE
> - ktrace_free(ip->i_btrace);
> -#endif
> -#ifdef XFS_RW_TRACE
> - ktrace_free(ip->i_rwtrace);
> -#endif
> -#ifdef XFS_ILOCK_TRACE
> - ktrace_free(ip->i_lock_trace);
> -#endif
> -#ifdef XFS_DIR2_TRACE
> - ktrace_free(ip->i_dir_trace);
> -#endif
> - if (ip->i_itemp) {
> - /*
> - * Only if we are shutting down the fs will we see an
> - * inode still in the AIL. If it is there, we should remove
> - * it to prevent a use-after-free from occurring.
> - */
> - xfs_log_item_t *lip = &ip->i_itemp->ili_item;
> - struct xfs_ail *ailp = lip->li_ailp;
> -
> - ASSERT(((lip->li_flags & XFS_LI_IN_AIL) == 0) ||
> - XFS_FORCED_SHUTDOWN(ip->i_mount));
> - if (lip->li_flags & XFS_LI_IN_AIL) {
> - spin_lock(&ailp->xa_lock);
> - if (lip->li_flags & XFS_LI_IN_AIL)
> - xfs_trans_ail_delete(ailp, lip);
> - else
> - spin_unlock(&ailp->xa_lock);
> - }
> - xfs_inode_item_destroy(ip);
> - ip->i_itemp = NULL;
> - }
> - /* asserts to verify all state is correct here */
> - ASSERT(atomic_read(&ip->i_iocount) == 0);
> - ASSERT(atomic_read(&ip->i_pincount) == 0);
> - ASSERT(!spin_is_locked(&ip->i_flags_lock));
> - ASSERT(completion_done(&ip->i_flush));
> - kmem_zone_free(xfs_inode_zone, ip);
> + xfs_inode_free(ip);
> }
>
> /*
> Index: linux-2.6/fs/xfs/xfs_inode.h
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_inode.h 2009-08-03 01:23:39.876532108 +0200
> +++ linux-2.6/fs/xfs/xfs_inode.h 2009-08-03 01:23:47.411789594 +0200
> @@ -310,26 +310,6 @@ static inline struct inode *VFS_I(struct
> }
>
> /*
> - * Get rid of a partially initialized inode.
> - *
> - * We have to go through destroy_inode to make sure allocations
> - * from init_inode_always like the security data are undone.
> - *
> - * We mark the inode bad so that it takes the short cut in
> - * the reclaim path instead of going through the flush path
> - * which doesn't make sense for an inode that has never seen the
> - * light of day.
> - */
> -static inline void xfs_destroy_inode(struct xfs_inode *ip)
> -{
> - struct inode *inode = VFS_I(ip);
> -
> - make_bad_inode(inode);
> - __destroy_inode(inode);
> - inode->i_sb->s_op->destroy_inode(inode);
> -}
> -
> -/*
> * i_flags helper functions
> */
> static inline void
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
next prev parent reply other threads:[~2009-08-06 23:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 14:15 [PATCH 0/4] XFS iget fixes Christoph Hellwig
2009-08-04 14:15 ` Christoph Hellwig
2009-08-04 14:15 ` [PATCH 1/4] xfs: fix locking in xfs_iget_cache_hit Christoph Hellwig
2009-08-04 14:15 ` Christoph Hellwig
2009-08-06 21:50 ` Eric Sandeen
2009-08-06 22:29 ` Christoph Hellwig
2009-08-07 17:25 ` Felix Blyakher
2009-08-07 17:25 ` Felix Blyakher
2009-08-10 17:09 ` Christoph Hellwig
2009-08-10 17:09 ` Christoph Hellwig
2009-08-16 21:01 ` Eric Sandeen
2009-08-16 21:01 ` Eric Sandeen
2009-08-16 22:54 ` Felix Blyakher
2009-08-16 22:54 ` Felix Blyakher
2009-08-17 0:36 ` Christoph Hellwig
2009-08-17 0:36 ` Christoph Hellwig
2009-08-17 3:05 ` Felix Blyakher
2009-08-17 3:05 ` Felix Blyakher
2009-08-04 14:15 ` [PATCH 2/4] fix inode_init_always calling convention Christoph Hellwig
2009-08-04 14:15 ` Christoph Hellwig
2009-08-06 22:30 ` Eric Sandeen
2009-08-06 22:30 ` Eric Sandeen
2009-08-07 17:39 ` Felix Blyakher
2009-08-07 17:39 ` Felix Blyakher
2009-08-07 18:09 ` Felix Blyakher
2009-08-07 18:09 ` Felix Blyakher
2009-08-04 14:15 ` [PATCH 3/4] add __destroy_inode Christoph Hellwig
2009-08-04 14:15 ` Christoph Hellwig
2009-08-06 22:56 ` Eric Sandeen
2009-08-06 22:56 ` Eric Sandeen
2009-08-07 18:20 ` Felix Blyakher
2009-08-07 18:20 ` Felix Blyakher
2009-08-04 14:15 ` [PATCH 4/4] xfs: add xfs_inode_free Christoph Hellwig
2009-08-04 14:15 ` Christoph Hellwig
2009-08-06 23:54 ` Eric Sandeen [this message]
2009-08-06 23:54 ` Eric Sandeen
2009-08-07 18:22 ` Felix Blyakher
2009-08-07 18:22 ` Felix Blyakher
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=4A7B6D4D.8090707@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.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.