From: Mark Tinguely <tinguely@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/5] Misc controversial patches
Date: Wed, 02 Jul 2014 09:32:06 -0500 [thread overview]
Message-ID: <20140702143206.438456679@sgi.com> (raw)
Here is a repost of these patches.
Patch one and two deal with EFIs getting stuck on the AIL and hanging
unmount. First deals with log recovery the other xfs_bmap_finish and
log write errors:
xfs-fix-efi-in-log-recovery-error.patch
xfs-fix-efi-on-filesystem-errors.patch
Patch three and four deal with resource leaks in failed log recoveries.
The first is a rewrite of Dave's rewrite of my patch with ideas from
Christoph. The second is taking care of leaked inode pointers:
xfs-fix-log-recovery-leaks.patch
xfs-reclaim-inodes-on-recovery-fail.patch
Lastly is the CIL sequence error. The setting of ctx->commit_lsn
in xlog_cil_init_post_recovery allows smaller cil push sequences finish
out of order:
xfs-fix-cil-push-seq-after-recovery.patch
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-07-02 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 14:32 Mark Tinguely [this message]
2014-07-02 14:32 ` [PATCH 1/5] xfs: remove efi from AIL in log recovery Mark Tinguely
2014-07-07 14:30 ` Brian Foster
2014-07-07 15:29 ` Mark Tinguely
2014-07-07 23:44 ` Dave Chinner
2014-07-02 14:32 ` [PATCH 2/5] xfs: free the EFI entries from AIL on forced shutdown Mark Tinguely
2014-07-02 14:32 ` [PATCH 3/5] xfs: free the list of recovery items on error Mark Tinguely
2014-07-02 14:32 ` [PATCH 4/5] xfs: free inodes on log recovery error Mark Tinguely
2014-07-07 14:30 ` Brian Foster
2014-07-07 15:18 ` Mark Tinguely
2014-07-09 9:02 ` Christoph Hellwig
2014-07-02 14:32 ` [PATCH 5/5] xfs: fix cil push sequence after log recovery Mark Tinguely
2014-07-07 15:26 ` 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=20140702143206.438456679@sgi.com \
--to=tinguely@sgi.com \
--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