linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Vagin <avagin@openvz.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Andrey Vagin <avagin@openvz.org>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	Pavel Emelyanov <xemul@parallels.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH] fs: show locked and lock_ro options in mountinfo
Date: Fri, 27 Mar 2015 23:39:34 +0300	[thread overview]
Message-ID: <1427488774-5077-1-git-send-email-avagin@openvz.org> (raw)

I don't see any reasons to hide them. This information can help to
understand errors.

And this information is required for correct checkpoint/restore of mount
namespaces.

Cc: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Pavel Emelyanov <xemul@parallels.com>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrey Vagin <avagin@openvz.org>
---
 fs/proc_namespace.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/fs/proc_namespace.c b/fs/proc_namespace.c
index 8db932d..ad86134 100644
--- a/fs/proc_namespace.c
+++ b/fs/proc_namespace.c
@@ -66,6 +66,8 @@ static void show_mnt_opts(struct seq_file *m, struct vfsmount *mnt)
 		{ MNT_NOATIME, ",noatime" },
 		{ MNT_NODIRATIME, ",nodiratime" },
 		{ MNT_RELATIME, ",relatime" },
+		{ MNT_LOCKED, ",locked" },
+		{ MNT_LOCK_READONLY, ",lock_ro"},
 		{ 0, NULL }
 	};
 	const struct proc_fs_info *fs_infop;
-- 
2.1.0


             reply	other threads:[~2015-03-27 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 20:39 Andrey Vagin [this message]
2015-03-27 21:42 ` [PATCH] fs: show locked and lock_ro options in mountinfo Richard Weinberger
2015-03-27 22:35   ` Andrey Wagin
2015-03-27 22:47     ` Richard Weinberger
2015-03-31 15:15       ` Andrey Wagin
2015-03-31 21:29         ` Eric W. Biederman

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=1427488774-5077-1-git-send-email-avagin@openvz.org \
    --to=avagin@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xemul@parallels.com \
    /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).