From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: regression fixes for 3.8 merge cycle
Date: Tue, 20 Nov 2012 22:27:09 +1100 [thread overview]
Message-ID: <1353410831-22653-1-git-send-email-david@fromorbit.com> (raw)
Folks,
Here's a couple of fixes for regressions reported in the past couple
of days. They've passed xfstests smoke testing here. I'm not really
certain whether the direct Io deadlock fix is the best way to fix
the problem, but I can't think of any other way of doing it at this
point because we have no way of passing a transaction context to the
direct IO allocation callback path. If anyone has any bright ideas,
I'm all ears....
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-11-20 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 11:27 Dave Chinner [this message]
2012-11-20 11:27 ` [PATCH 1/2] xfs: inode allocation should use unmapped buffers Dave Chinner
2012-11-20 15:57 ` Christoph Hellwig
2012-11-20 11:27 ` [PATCH 2/2] xfs: fix direct IO nested transaction deadlock Dave Chinner
2012-11-20 16:10 ` Christoph Hellwig
2012-11-20 16:37 ` Jan Kara
2012-11-20 19:53 ` Dave Chinner
2012-11-21 9:59 ` Christoph Hellwig
2012-11-22 0:48 ` 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=1353410831-22653-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