linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 3.4
Date: Tue, 27 Mar 2012 16:11:57 +0200	[thread overview]
Message-ID: <cover.1332852833.git.list.btrfs@jan-o-sch.net> (raw)

Hi Chris,

please pull my three current patches from my repo, based on your
for-linus branch (I can rebase them to the integration branch if that
helps):

	git://git.jan-o-sch.net/btrfs-unstable for-chris

It's two really small fixes both mentioned earlier and a more or less
imporant fixup for scrub. While working fine in 3.2, name resolving can
deadlock since the first rc of 3.3. I suggest we queue that patch 3/3
for submission to 3.3-stable.

I'm passing xfstests just as good as for-linus is doing without my
patches (which is not really good). I also made some manual error
insertion tests to verify that the scrub deadlock chance is really gone.

And, we really should have an xfstest for raid-repair and scrub-repair.
Anyone? :-)

-Jan

Jan Schmidt (3):
  Btrfs: actually call btrfs_init_lockdep
  Btrfs: check return value of btrfs_cow_block()
  Btrfs: fix regression in scrub path resolving

 fs/btrfs/backref.c     |  115 +++++++++++++++++++++++++++--------------------
 fs/btrfs/backref.h     |    5 +-
 fs/btrfs/ioctl.c       |    4 +-
 fs/btrfs/scrub.c       |    4 +-
 fs/btrfs/super.c       |    2 +
 fs/btrfs/transaction.c |    6 ++-
 6 files changed, 79 insertions(+), 57 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2012-03-27 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 14:11 Jan Schmidt [this message]
2012-03-27 14:11 ` [PATCH 1/3] Btrfs: actually call btrfs_init_lockdep Jan Schmidt
2012-03-27 14:11 ` [PATCH 2/3] Btrfs: check return value of btrfs_cow_block() Jan Schmidt
2012-03-27 14:12 ` [PATCH 3/3] Btrfs: fix regression in scrub path resolving Jan Schmidt

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=cover.1332852833.git.list.btrfs@jan-o-sch.net \
    --to=list.btrfs@jan-o-sch.net \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).