From: Sage Weil <sage@inktank.com>
To: linux-btrfs@vger.kernel.org
Cc: Sage Weil <sage@inktank.com>
Subject: [PATCH 0/3] lockdep fixups for sb_interval#2 vs async transaction commit
Date: Thu, 30 Aug 2012 15:26:14 -0700 [thread overview]
Message-ID: <1346365577-9405-1-git-send-email-sage@inktank.com> (raw)
These three patches (in combination with btrfs-next) fix things up for me!
Sage Weil (3):
Btrfs: pass lockdep rwsem metadata to async commit transaction
Btrfs: set journal_info in async trans commit worker
Btrfs: do not take cleanup_work_sem in btrfs_run_delayed_iputs()
fs/btrfs/inode.c | 2 --
fs/btrfs/transaction.c | 18 ++++++++++++++++++
2 files changed, 18 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-08-30 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 22:26 Sage Weil [this message]
2012-08-30 22:26 ` [PATCH 1/3] Btrfs: pass lockdep rwsem metadata to async commit transaction Sage Weil
2012-08-30 22:26 ` [PATCH 2/3] Btrfs: set journal_info in async trans commit worker Sage Weil
2012-08-30 22:26 ` [PATCH 3/3] Btrfs: do not take cleanup_work_sem in btrfs_run_delayed_iputs() Sage Weil
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=1346365577-9405-1-git-send-email-sage@inktank.com \
--to=sage@inktank.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).