[PATCH] eCryptfs: Remove debugging cruft

[Michael Halcrow <mhalcrow@us.ibm.com>]

We let a few debugging statements slip into patch
``ecryptfs-more-intelligent-use-of-tfm-objects''. This patch removes
some extra printk's in the log on mount and unmount.

Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>

---

 fs/ecryptfs/crypto.c |    1 -
 fs/ecryptfs/main.c   |    3 ---
 fs/ecryptfs/super.c  |    1 -
 3 files changed, 0 insertions(+), 5 deletions(-)

2d3209f0eb0011f12115d50283b9728e5045a9d1
diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
index 626a4c7..427f470 100644
--- a/fs/ecryptfs/crypto.c
+++ b/fs/ecryptfs/crypto.c
@@ -186,7 +186,6 @@ void ecryptfs_destruct_crypt_stat(struct
 void ecryptfs_destruct_mount_crypt_stat(
 	struct ecryptfs_mount_crypt_stat *mount_crypt_stat)
 {
-	printk(KERN_INFO "%s\n", __FUNCTION__);
 	if (mount_crypt_stat->global_auth_tok_key)
 		key_put(mount_crypt_stat->global_auth_tok_key);
 	if (mount_crypt_stat->global_key_tfm)
diff --git a/fs/ecryptfs/main.c b/fs/ecryptfs/main.c
index 7598ba0..3592834 100644
--- a/fs/ecryptfs/main.c
+++ b/fs/ecryptfs/main.c
@@ -536,9 +536,6 @@ out:
  */
 static void ecryptfs_kill_block_super(struct super_block *sb)
 {
-	printk(KERN_INFO "%s\n", __FUNCTION__);
-/*	ecryptfs_destruct_mount_crypt_stat(
-	&(ecryptfs_superblock_to_private(sb)->mount_crypt_stat)); */
 	generic_shutdown_super(sb);
 }
 
diff --git a/fs/ecryptfs/super.c b/fs/ecryptfs/super.c
index b60bf07..afca9c6 100644
--- a/fs/ecryptfs/super.c
+++ b/fs/ecryptfs/super.c
@@ -108,7 +108,6 @@ static void ecryptfs_put_super(struct su
 {
 	struct ecryptfs_sb_info *sb_info = ecryptfs_superblock_to_private(sb);
 
-	printk(KERN_INFO "%s\n", __FUNCTION__);
 	mntput(sb_info->lower_mnt);
 	ecryptfs_destruct_mount_crypt_stat(&sb_info->mount_crypt_stat);
 	kmem_cache_free(ecryptfs_sb_info_cache, sb_info);
-- 
1.3.3

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/