From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fix ioctl-initiated transactions vs wait_current_trans() deadlock
Date: Mon, 04 Aug 2008 09:01:59 -0400 [thread overview]
Message-ID: <1217854920.29139.57.camel@think.oraclecorp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808021135050.23304@cobra.newdream.net>
On Sat, 2008-08-02 at 12:39 -0700, Sage Weil wrote:
> Hi Chris,
>
> Commit 597:466b27332893 (btrfs_start_transaction: wait for commits in
> progress) breaks the transaction start/stop ioctls by making
> btrfs_start_transaction conditionally wait for the next transaction to
> start. If an application artificially is holding a transaction open,
> things deadlock.
>
Right, once I was done tuning the throttle code I was going to email you
on this. Your patch looks pretty good, I'll take it in today.
-chris
prev parent reply other threads:[~2008-08-04 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 19:39 [PATCH] fix ioctl-initiated transactions vs wait_current_trans() deadlock Sage Weil
2008-08-04 13:01 ` Chris Mason [this message]
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=1217854920.29139.57.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/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