linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Fwd: [PATCH v2] btrfs: add mount umount logs
Date: Thu, 13 Jul 2017 15:22:18 +0800	[thread overview]
Message-ID: <3352043d-dbb1-0055-f50a-c91ca43aff1d@oracle.com> (raw)
In-Reply-To: <1497518442-1078-1-git-send-email-anand.jain@oracle.com>


Hi David, Any response on this ?

Thanks, Anand

-------- Forwarded Message --------
Subject: [PATCH v2] btrfs: add mount umount logs
Date: Thu, 15 Jun 2017 17:20:42 +0800
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
CC: dsterba@suse.cz

From: Anand Jain <Anand.Jain@oracle.com>

By looking at the logs we should be able to know when FS was
mounted and unmounted and the options used, so to help forensic
investigations.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
Hi David,

  As you suggested VFS is definitely a better place to have this
  and its patch is in the ML. But I am not too sure what's their
  plan is.  So can we integrate this into BTRFS ? as we can always
  remove it once VFS provides that feature.

Thanks, Anand

v2: Use ro,rw instead of rdonly and directly print it.

  fs/btrfs/super.c | 13 +++++++++++++
  1 file changed, 13 insertions(+)

diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 3371213924bd..2cb367a106e3 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -1373,6 +1373,13 @@ static char *setup_root_args(char *args)
  	return buf;
  }
  +static void print_mount_info(struct btrfs_fs_info *info, int flag, 
char *opt,
+		char *prefix)
+{
+	btrfs_notice(info, "%s: flags=%s opt=%s\n",
+			prefix, flag & MS_RDONLY ? "ro":"rw", opt);
+}
+
  static struct dentry *mount_subvol(const char *subvol_name, u64 
subvol_objectid,
  				   int flags, const char *device_name,
  				   char *data)
@@ -1467,6 +1474,8 @@ static struct dentry *mount_subvol(const char 
*subvol_name, u64 subvol_objectid,
  			dput(root);
  			root = ERR_PTR(ret);
  			deactivate_locked_super(s);
+		} else {
+			print_mount_info(fs_info, flags, data, "mount");
  		}
  	}
  @@ -1845,6 +1854,9 @@ static int btrfs_remount(struct super_block *sb, 
int *flags, char *data)
  out:
  	wake_up_process(fs_info->transaction_kthread);
  	btrfs_remount_cleanup(fs_info, old_opts);
+
+	print_mount_info(fs_info, *flags, data, "remount");
+
  	return 0;
   restore:
@@ -2174,6 +2186,7 @@ static int btrfs_statfs(struct dentry *dentry, 
struct kstatfs *buf)
  static void btrfs_kill_super(struct super_block *sb)
  {
  	struct btrfs_fs_info *fs_info = btrfs_sb(sb);
+	btrfs_notice(fs_info, "%s\n", "unmount");
  	kill_anon_super(sb);
  	free_fs_info(fs_info);
  }
-- 
2.7.0

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

      reply	other threads:[~2017-07-13  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  9:20 [PATCH v2] btrfs: add mount umount logs Anand Jain
2017-07-13  7:22 ` Anand Jain [this message]

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=3352043d-dbb1-0055-f50a-c91ca43aff1d@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).