From: Jan Kara <jack@suse.cz>
To: Ben Myers <bpm@sgi.com>
Cc: Jan Kara <jack@suse.cz>, Alex Elder <elder@kernel.org>,
stable@kernel.org, xfs@oss.sgi.com
Subject: [PATCH v2] xfs: Fix oops on IO error during xlog_recover_process_iunlinks()
Date: Thu, 15 Mar 2012 09:55:05 +0100 [thread overview]
Message-ID: <1331801705-1145-1-git-send-email-jack@suse.cz> (raw)
When an IO error happens during inode deletion run from
xlog_recover_process_iunlinks() filesystem gets shutdown. Thus any subsequent
attempt to read buffers fails. Code in xlog_recover_process_iunlinks() does not
count with the fact that read of a buffer which was read a while ago can
really fail which results in the oops on
agi = XFS_BUF_TO_AGI(agibp);
Fix the problem by cleaning up the buffer handling in
xlog_recover_process_iunlinks() as suggested by Dave Chinner. We release buffer
lock but keep buffer reference to AG buffer. That is enough for buffer stay
pinned in memory and we don't have to call xfs_read_agi() all the time.
CC: stable@kernel.org
Signed-off-by: Jan Kara <jack@suse.cz>
---
fs/xfs/xfs_log_recover.c | 34 ++++++++++++----------------------
1 files changed, 12 insertions(+), 22 deletions(-)
Last time I sent this patch as a reply to Dave's email and apparently the
patch didn't catch the attention. So I'm resending it now.
diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
index 0ed9ee7..0827644 100644
--- a/fs/xfs/xfs_log_recover.c
+++ b/fs/xfs/xfs_log_recover.c
@@ -3161,37 +3161,27 @@ xlog_recover_process_iunlinks(
*/
continue;
}
+ /*
+ * Take an extra reference to the buffer and then release it
+ * to drop the lock so that it can be acquired in the normal
+ * course of the transaction to truncate and free each
+ * inode. Because we are not racing with anyone else here
+ * for the AGI buffer, we don't even need to hold it locked
+ * to read the initial unlinked bucket entries out of the
+ * buffer.
+ */
agi = XFS_BUF_TO_AGI(agibp);
+ xfs_buf_hold(agibp);
+ xfs_buf_relse(agibp);
for (bucket = 0; bucket < XFS_AGI_UNLINKED_BUCKETS; bucket++) {
agino = be32_to_cpu(agi->agi_unlinked[bucket]);
while (agino != NULLAGINO) {
- /*
- * Release the agi buffer so that it can
- * be acquired in the normal course of the
- * transaction to truncate and free the inode.
- */
- xfs_buf_relse(agibp);
-
agino = xlog_recover_process_one_iunlink(mp,
agno, agino, bucket);
-
- /*
- * Reacquire the agibuffer and continue around
- * the loop. This should never fail as we know
- * the buffer was good earlier on.
- */
- error = xfs_read_agi(mp, NULL, agno, &agibp);
- ASSERT(error == 0);
- agi = XFS_BUF_TO_AGI(agibp);
}
}
-
- /*
- * Release the buffer for the current agi so we can
- * go on to the next one.
- */
- xfs_buf_relse(agibp);
+ xfs_buf_rele(agibp);
}
mp->m_dmevmask = mp_dmevmask;
--
1.7.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-03-15 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 8:55 Jan Kara [this message]
2012-03-15 9:08 ` [PATCH v2] xfs: Fix oops on IO error during xlog_recover_process_iunlinks() Christoph Hellwig
2012-03-15 9:19 ` Jan Kara
2012-03-15 22:07 ` Dave Chinner
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=1331801705-1145-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox