From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: fix error handling in xlog_recover_process_one_iunlink
Date: Wed, 12 Nov 2008 06:43:51 -0500 [thread overview]
Message-ID: <20081112114351.GA15216@infradead.org> (raw)
If we fail after xfs_iget we have to drop the reference count, spotted
by Dave Chinner. Also remove some useless asserts and stop trying to
deal with di_mode == 0 inodes because never gets those without passing
the IGET_CREATE flag to xfs_iget.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6-xfs/fs/xfs/xfs_log_recover.c
===================================================================
--- linux-2.6-xfs.orig/fs/xfs/xfs_log_recover.c 2008-11-12 11:05:22.000000000 +0100
+++ linux-2.6-xfs/fs/xfs/xfs_log_recover.c 2008-11-12 11:05:54.000000000 +0100
@@ -3147,13 +3147,12 @@ xlog_recover_process_one_iunlink(
/*
* Get the on disk inode to find the next inode in the bucket.
*/
- ASSERT(ip != NULL);
error = xfs_itobp(mp, NULL, ip, &dip, &ibp, XFS_BUF_LOCK);
if (error)
- goto fail;
+ goto fail_iput;
- ASSERT(dip != NULL);
ASSERT(ip->i_d.di_nlink == 0);
+ ASSERT(ip->i_d.di_mode != 0);
/* setup for the next pass */
agino = be32_to_cpu(dip->di_next_unlinked);
@@ -3165,18 +3164,11 @@ xlog_recover_process_one_iunlink(
*/
ip->i_d.di_dmevmask = 0;
- /*
- * If this is a new inode, handle it specially. Otherwise, just
- * drop our reference to the inode. If there are no other
- * references, this will send the inode to xfs_inactive() which
- * will truncate the file and free the inode.
- */
- if (ip->i_d.di_mode == 0)
- xfs_iput_new(ip, 0);
- else
- IRELE(ip);
+ IRELE(ip);
return agino;
+ fail_iput:
+ IRELE(ip);
fail:
/*
* We can't read in the inode this bucket points to, or this inode
next reply other threads:[~2008-11-12 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 11:43 Christoph Hellwig [this message]
2008-11-21 20:44 ` fix error handling in xlog_recover_process_one_iunlink 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=20081112114351.GA15216@infradead.org \
--to=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.