summaryrefslogtreecommitdiffstats
path: root/fs/jffs2/gc.c
diff options
context:
space:
mode:
authorKaiGai Kohei <kaigai@ak.jp.nec.com>2006-05-13 15:16:13 +0900
committerKaiGai Kohei <kaigai@ak.jp.nec.com>2006-05-13 15:16:13 +0900
commit084702e00111eb9ffb6d8a5c1938b8e5423e40a8 (patch)
tree42f5842eb6f5373b04c4f4d254fde0bdcea2a4d5 /fs/jffs2/gc.c
parent8f2b6f49c656dd4597904f8c20661d6b73cdbbeb (diff)
downloadblackbird-op-linux-084702e00111eb9ffb6d8a5c1938b8e5423e40a8.tar.gz
blackbird-op-linux-084702e00111eb9ffb6d8a5c1938b8e5423e40a8.zip
[JFFS2][XATTR] Remove jffs2_garbage_collect_xattr(c, ic)
Remove jffs2_garbage_collect_xattr(c, ic). jffs2_garbage_collect_xattr_datum/ref() are called from gc.c directly. In original implementation, jffs2_garbage_collect_xattr(c, ic) returns with holding a spinlock if 'ic' is inode_cache. But it returns after releasing a spinlock if 'ic' is xattr_datum/ref. It looks so confusable behavior. Thus, this patch makes caller manage locking/unlocking. [5/10] jffs2-xattr-v5.1-05-update_xattr_gc.patch Signed-off-by: KaiGai Kohei <kaigai@ak.jp.nec.com>
Diffstat (limited to 'fs/jffs2/gc.c')
-rw-r--r--fs/jffs2/gc.c21
1 files changed, 14 insertions, 7 deletions
diff --git a/fs/jffs2/gc.c b/fs/jffs2/gc.c
index 4ea1b7f0ae78..a5ef9814f165 100644
--- a/fs/jffs2/gc.c
+++ b/fs/jffs2/gc.c
@@ -266,15 +266,22 @@ int jffs2_garbage_collect_pass(struct jffs2_sb_info *c)
ic = jffs2_raw_ref_to_ic(raw);
+#ifdef CONFIG_JFFS2_FS_XATTR
/* When 'ic' refers xattr_datum/xattr_ref, this node is GCed as xattr.
- We can decide whether this node is inode or xattr by ic->class.
- ret = 0 : ic is xattr_datum/xattr_ref, and GC was SUCCESSED.
- ret < 0 : ic is xattr_datum/xattr_ref, but GC was FAILED.
- ret > 0 : ic is NOT xattr_datum/xattr_ref.
- */
- ret = jffs2_garbage_collect_xattr(c, ic);
- if (ret <= 0)
+ * We can decide whether this node is inode or xattr by ic->class. */
+ if (ic->class == RAWNODE_CLASS_XATTR_DATUM
+ || ic->class == RAWNODE_CLASS_XATTR_REF) {
+ BUG_ON(raw->next_in_ino != (void *)ic);
+ spin_unlock(&c->erase_completion_lock);
+
+ if (ic->class == RAWNODE_CLASS_XATTR_DATUM) {
+ ret = jffs2_garbage_collect_xattr_datum(c, (struct jffs2_xattr_datum *)ic);
+ } else {
+ ret = jffs2_garbage_collect_xattr_ref(c, (struct jffs2_xattr_ref *)ic);
+ }
goto release_sem;
+ }
+#endif
/* We need to hold the inocache. Either the erase_completion_lock or
the inocache_lock are sufficient; we trade down since the inocache_lock
OpenPOWER on IntegriCloud