public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/4] xfs: candidate fixes for 3.12-rc4
Date: Mon, 30 Sep 2013 09:37:02 +1000	[thread overview]
Message-ID: <1380497826-13474-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

The first two patches are regressions and hence -rc4 candidates -
the first patch fixes a lockdep false positive as a result of adding
the third quota inode, and the second fixes a on-disk format
interpretation problem in the v4 superblock dtype-in-dirent feature.

The third patch fixes the AGF vs AGI lock inversion problem I
reported a short while ago, and the last reduces the overhead of
atomic version change accounting. These two aren't critical fixes,
but would be nice to have out there for 3.12.

Cheers,

Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-09-29 23:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 23:37 Dave Chinner [this message]
2013-09-29 23:37 ` [PATCH 1/4] xfs: lockdep needs to know about 3 dquot-deep nesting Dave Chinner
2013-09-30 21:19   ` Ben Myers
2013-09-29 23:37 ` [PATCH 2/4] xfs: dirent dtype presence is dependent on directory magic numbers Dave Chinner
2013-09-30 22:02   ` Ben Myers
2013-10-18 16:56   ` Rich Johnston
2013-10-18 22:30     ` Dave Chinner
2013-10-18 22:41       ` Rich Johnston
2013-09-29 23:37 ` [PATCH 3/4] xfs: xfs_remove deadlocks due to inverted AGF vs AGI lock ordering Dave Chinner
2013-09-30 22:14   ` Ben Myers
2013-10-01 10:57     ` Dave Chinner
2013-09-29 23:37 ` [PATCH 4/4] xfs: open code inc_inode_iversion when logging an inode Dave Chinner
2013-09-30 22:24   ` Eric Sandeen
2013-09-30 22:39     ` Ben Myers
2013-10-01 11:12       ` Dave Chinner
2013-10-01 23:04         ` Ben Myers
2013-09-30 22:52 ` [PATCH 0/4] xfs: candidate fixes for 3.12-rc4 Ben Myers

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=1380497826-13474-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