From: Michael Halcrow <mhalcrow@us.ibm.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] eCryptfs: Remove debugging cruft
Date: Thu, 22 Jun 2006 17:09:45 -0500 [thread overview]
Message-ID: <20060622220945.GD2817@us.ibm.com> (raw)
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
reply other threads:[~2006-06-22 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060622220945.GD2817@us.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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