* [PATCH] Btrfs: don't set current->journal_info for ioctl trans handles
@ 2009-11-03 15:01 Josef Bacik
0 siblings, 0 replies; only message in thread
From: Josef Bacik @ 2009-11-03 15:01 UTC (permalink / raw)
To: linux-btrfs; +Cc: chris.mason
We use journal_info to tell if we're in a nested transaction to make sure we
don't commit the transaction within a nested transaction. We use another
method to see if there are any outstanding ioctl trans handles, so if we're
starting one do not set current->journal_info, since it will screw with other
filesystems.
Signed-off-by: Josef Bacik <josef@redhat.com>
---
fs/btrfs/transaction.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
index bca82a4..3d3dcea 100644
--- a/fs/btrfs/transaction.c
+++ b/fs/btrfs/transaction.c
@@ -186,7 +186,7 @@ static struct btrfs_trans_handle *start_transaction(struct btrfs_root *root,
h->alloc_exclude_start = 0;
h->delayed_ref_updates = 0;
- if (!current->journal_info)
+ if (!current->journal_info && wait != 2)
current->journal_info = h;
root->fs_info->running_transaction->use_count++;
--
1.5.4.3
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2009-11-03 15:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-03 15:01 [PATCH] Btrfs: don't set current->journal_info for ioctl trans handles Josef Bacik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox