All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: skinsbursky@virtuozzo.com
Cc: criu@openvz.org, autofs@vger.kernel.org,
	linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] autofs: show pipe inode in mount options
Date: Fri, 08 Jan 2016 15:20:40 +0800	[thread overview]
Message-ID: <1452237640.2973.19.camel@themaw.net> (raw)
In-Reply-To: <568E8840.3010801@odin.com>

On Thu, 2016-01-07 at 16:46 +0100, Stanislav Kinsburskiy wrote:
> Good day, gentlemen.
> 
> Could you update, what's the status with this patch?
> Without it it's impossible to match process pipe with kernel pipe,
> while 
> this is "must have" to be able to migrate AutoFS via CRIU.

Right, I did mean to reply to this mail but have been distracted by
family stuff.

I don't know what CRIU is and people looking at changelog entries
shouldn't need to do a web search to find out.

Could you change it a little.

I'm also not sure whether to forward this (assuming the description is
updated a little) to Al or to include it in the series to rename
autofs4 to autofs that I'm hoping to ask be included in linux-next
fairly soon.

Passing it on to Al will likely interfere with the series coming from
linux-next so that could be bit of a hassle.

Another thing I'm wondering about is the order this entry will appear
at in the options. You order choice is sensible though and autofs
shouldn't have a problem with the inserted option but other
applications might.

Finally, and perhaps most importantly, I don't get what your trying to
do, you also haven't given any clues to that in the patch dscription.

IOW how do you expect to use this.

> 
> 
> 16.12.2015 13:02, Stanislav Kinsburskiy пишет:
> > This is required for CRIU to migrate a mount point, when write end
> > in user
> > space is closed.

Like I said what does this mean.

autofs doesn't need this when it re-constructs a mount tree from
existing mounts on re-start or after a SIGKILL on the automount
process.

How is this different and how will it be used?

The question to be answered here is "is this the best way to do it and
will it work for the autofs mount types you expect it to"?

> > 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));
> > 
> 
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

WARNING: multiple messages have this Message-ID (diff)
From: Ian Kent <raven@themaw.net>
To: skinsbursky@virtuozzo.com
Cc: criu@openvz.org, autofs@vger.kernel.org,
	linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] autofs: show pipe inode in mount options
Date: Fri, 08 Jan 2016 15:20:40 +0800	[thread overview]
Message-ID: <1452237640.2973.19.camel@themaw.net> (raw)
In-Reply-To: <568E8840.3010801@odin.com>

On Thu, 2016-01-07 at 16:46 +0100, Stanislav Kinsburskiy wrote:
> Good day, gentlemen.
> 
> Could you update, what's the status with this patch?
> Without it it's impossible to match process pipe with kernel pipe,
> while 
> this is "must have" to be able to migrate AutoFS via CRIU.

Right, I did mean to reply to this mail but have been distracted by
family stuff.

I don't know what CRIU is and people looking at changelog entries
shouldn't need to do a web search to find out.

Could you change it a little.

I'm also not sure whether to forward this (assuming the description is
updated a little) to Al or to include it in the series to rename
autofs4 to autofs that I'm hoping to ask be included in linux-next
fairly soon.

Passing it on to Al will likely interfere with the series coming from
linux-next so that could be bit of a hassle.

Another thing I'm wondering about is the order this entry will appear
at in the options. You order choice is sensible though and autofs
shouldn't have a problem with the inserted option but other
applications might.

Finally, and perhaps most importantly, I don't get what your trying to
do, you also haven't given any clues to that in the patch dscription.

IOW how do you expect to use this.

> 
> 
> 16.12.2015 13:02, Stanislav Kinsburskiy пишет:
> > This is required for CRIU to migrate a mount point, when write end
> > in user
> > space is closed.

Like I said what does this mean.

autofs doesn't need this when it re-constructs a mount tree from
existing mounts on re-start or after a SIGKILL on the automount
process.

How is this different and how will it be used?

The question to be answered here is "is this the best way to do it and
will it work for the autofs mount types you expect it to"?

> > 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));
> > 
> 

  reply	other threads:[~2016-01-08  7:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 12:02 [PATCH] autofs: show pipe inode in mount options Stanislav Kinsburskiy
2016-01-07 15:46 ` Stanislav Kinsburskiy
2016-01-07 15:46   ` Stanislav Kinsburskiy
2016-01-08  7:20   ` Ian Kent [this message]
2016-01-08  7:20     ` Ian Kent
2016-01-08 11:29     ` Stanislav Kinsburskiy
2016-01-08 11:29       ` Stanislav Kinsburskiy
2016-01-08 12:58       ` Ian Kent
2016-01-08 12:58         ` Ian Kent
2016-01-08 15:05         ` Stanislav Kinsburskiy
2016-01-08 15:05           ` Stanislav Kinsburskiy
2016-01-09  1:31           ` Ian Kent
2016-01-09  1:31             ` Ian Kent
2016-01-11 11:33             ` Stanislav Kinsburskiy
2016-01-11 11:33               ` Stanislav Kinsburskiy
2016-01-22 11:34               ` 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 11:30                     ` Stanislav Kinsburskiy
2016-01-25 23:19                   ` Stephen Rothwell
2016-01-25 23:48                     ` Andrew Morton
2016-01-25 23:48                       ` Andrew Morton
2016-01-26  3:55                       ` Ian Kent
2016-01-26  3:55                         ` Ian Kent
2016-02-02  4:43                         ` 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=1452237640.2973.19.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=criu@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skinsbursky@virtuozzo.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.