From 638cdd3ae567d38576022a8bb21161253e6b84f7 Mon Sep 17 00:00:00 2001
From: Miao Xie <miaox@cn.fujitsu.com>
Date: Tue, 29 Jan 2013 10:05:05 +0000
Subject: [PATCH] --- yaml --- r: 360411 b: refs/heads/master c:
 8c6a3ee6dbd564d05019d396ecb5dc5b35cbc273 h: refs/heads/master i:   360409:
 239917cd1dab35b54133d911cdc84b77ccc8f774   360407:
 9cf6991668d3be015eec8017226b7bd131a77ed1 v: v3

---
 [refs]                 | 2 +-
 trunk/fs/btrfs/ctree.h | 6 ++++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/[refs] b/[refs]
index b9ea4577c980..8789f83c2c11 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 55e301fd57a6239ec14b91a1cf2e70b3dd135194
+refs/heads/master: 8c6a3ee6dbd564d05019d396ecb5dc5b35cbc273
diff --git a/trunk/fs/btrfs/ctree.h b/trunk/fs/btrfs/ctree.h
index 69321013683c..169baa817d96 100644
--- a/trunk/fs/btrfs/ctree.h
+++ b/trunk/fs/btrfs/ctree.h
@@ -1297,6 +1297,12 @@ struct btrfs_fs_info {
 	u64 last_trans_log_full_commit;
 	unsigned long mount_opt;
 	unsigned long compress_type:4;
+	/*
+	 * It is a suggestive number, the read side is safe even it gets a
+	 * wrong number because we will write out the data into a regular
+	 * extent. The write side(mount/remount) is under ->s_umount lock,
+	 * so it is also safe.
+	 */
 	u64 max_inline;
 	u64 alloc_start;
 	struct btrfs_transaction *running_transaction;