From: Stanislav Kinsburskiy <skinsbursky@virtuozzo.com>
To: raven@themaw.net
Cc: criu@openvz.org, autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] autofs: show pipe inode in mount options
Date: Wed, 16 Dec 2015 16:02:28 +0400 [thread overview]
Message-ID: <20151216120222.19097.54512.stgit@localhost.localdomain> (raw)
This is required for CRIU to migrate a mount point, when write end in user
space is closed.
To be able to migrate such mount, read end of the pipe have to be searched
within autofs master process, and pipe inode will be used as a key.
Signed-off-by: Stanislav Kinsburskiy <skinsbursky@virtuozzo.com>
---
fs/autofs4/inode.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/autofs4/inode.c b/fs/autofs4/inode.c
index a3ae0b2..16f875a 100644
--- a/fs/autofs4/inode.c
+++ b/fs/autofs4/inode.c
@@ -77,6 +77,10 @@ static int autofs4_show_options(struct seq_file *m, struct dentry *root)
return 0;
seq_printf(m, ",fd=%d", sbi->pipefd);
+ if (sbi->pipe)
+ seq_printf(m, ",pipe_ino=%ld", sbi->pipe->f_inode->i_ino);
+ else
+ seq_printf(m, ",pipe_ino=-1");
if (!uid_eq(root_inode->i_uid, GLOBAL_ROOT_UID))
seq_printf(m, ",uid=%u",
from_kuid_munged(&init_user_ns, root_inode->i_uid));
next reply other threads:[~2015-12-16 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 12:02 Stanislav Kinsburskiy [this message]
2016-01-07 15:46 ` [PATCH] autofs: show pipe inode in mount options Stanislav Kinsburskiy
2016-01-08 7:20 ` Ian Kent
2016-01-08 11:29 ` Stanislav Kinsburskiy
2016-01-08 12:58 ` Ian Kent
2016-01-08 15:05 ` Stanislav Kinsburskiy
2016-01-09 1:31 ` Ian Kent
2016-01-11 11:33 ` Stanislav Kinsburskiy
2016-01-22 11:34 ` Stanislav Kinsburskiy
2016-01-23 0:30 ` Ian Kent
2016-01-23 0:57 ` Ian Kent
2016-01-25 11:30 ` Stanislav Kinsburskiy
2016-01-25 23:19 ` Stephen Rothwell
2016-01-25 23:48 ` Andrew Morton
2016-01-26 3:55 ` Ian Kent
2016-02-02 4:43 ` Ian Kent
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=20151216120222.19097.54512.stgit@localhost.localdomain \
--to=skinsbursky@virtuozzo.com \
--cc=autofs@vger.kernel.org \
--cc=criu@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).