From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/5] xfs: fixes for 2.6.37-rcX
Date: Mon, 29 Nov 2010 11:20:19 +1100 [thread overview]
Message-ID: <1290990024-15898-1-git-send-email-david@fromorbit.com> (raw)
Alex,
This is my curent set of fixes needed for 2.6.37-rcX. I've already posted the
truncation fix and the stale buffer fixes, as well as the xfs_error_test
optimisation. The other two fixes I have extracted from my current scalability
patch set. They correct the invalid assumption that that ther eare no delayed
allocation blocks left on a file after writeback and prevent stale inodes from
being re-inserted into the AIL after the stale buffer behind them has been torn
down.
Let me know how you want me to post the final versions for you to pull into the
XFS tree. (i.e. do you want them in a git tree branch?)
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-29 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:20 Dave Chinner [this message]
2010-11-29 0:20 ` [PATCH 1/5] xfs: fix failed write truncation handling Dave Chinner
2010-11-29 0:20 ` [PATCH 2/5] xfs: push stale, pinned buffers on trylock failures Dave Chinner
2010-11-29 0:20 ` [PATCH 3/5] xfs: delayed alloc blocks beyond EOF are valid after writeback Dave Chinner
2010-11-29 8:04 ` Christoph Hellwig
2010-11-29 0:20 ` [PATCH 4/5] xfs: avoid moving stale inodes in the AIL Dave Chinner
2010-11-29 8:13 ` Christoph Hellwig
2010-11-29 0:20 ` [PATCH 5/5] xfs: only run xfs_error_test if error injection is active Dave Chinner
2010-11-29 8:13 ` Christoph Hellwig
2010-11-30 7:09 ` [PATCH 0/5] xfs: fixes for 2.6.37-rcX 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=1290990024-15898-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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