From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs; fixes for 2.7.37-rc4
Date: Wed, 24 Nov 2010 22:24:31 +1100 [thread overview]
Message-ID: <1290597873-5807-1-git-send-email-david@fromorbit.com> (raw)
The following two patches are bugs fixes needed for 2.6.37. The first fixes the
write truncation problem, and has been updated to pass blocks rather than byte
ranges into the punch function. The second fixes a log hang triggered by AIL
pushing being unable to move a locked, pinned and stale buffer from the tail of
the log and hence free up log space. Both of these fixes are candidates for a
2.6.36.y stable release.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-24 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 11:24 Dave Chinner [this message]
2010-11-24 11:24 ` [PATCH 1/2] xfs: fix failed write truncation handling Dave Chinner
2010-11-24 17:21 ` Christoph Hellwig
2010-11-24 11:24 ` [PATCH 2/2] xfs: push stale, pinned buffers on trylock failures Dave Chinner
2010-11-24 17:20 ` Christoph Hellwig
2010-11-25 0:23 ` Dave Chinner
2010-11-25 0:28 ` [PATCH v2] " Dave Chinner
2010-11-25 7:37 ` Christoph Hellwig
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=1290597873-5807-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