Linux Container Development
 help / color / mirror / Atom feed
From: Mateusz Guzik <mguzik-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: James Bottomley
	<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: linux-fsdevel
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Subject: Re: [Patch v2 1/3] fs: add filp_clone_open API
Date: Tue, 8 Mar 2016 10:17:07 +0100	[thread overview]
Message-ID: <20160308091705.GB2189@mguzik> (raw)
In-Reply-To: <1456429008.2377.4.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>

On Thu, Feb 25, 2016 at 11:36:48AM -0800, James Bottomley wrote:
> I need an API that allows me to obtain a clone of the current file
> pointer to pass in to an exec handler.  I've labelled this as an
> internal API because I can't see how it would be useful outside of the
> fs subsystem.  The use case will be a persistent binfmt_misc handler.
> 
> Signed-off-by: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
> ---
>  fs/internal.h |  1 +
>  fs/open.c     | 20 ++++++++++++++++++++
>  2 files changed, 21 insertions(+)
> 
> diff --git a/fs/internal.h b/fs/internal.h
> index b71deee..c8ca0c9 100644
> --- a/fs/internal.h
> +++ b/fs/internal.h
> @@ -108,6 +108,7 @@ extern long do_handle_open(int mountdirfd,
>  			   struct file_handle __user *ufh, int open_flag);
>  extern int open_check_o_direct(struct file *f);
>  extern int vfs_open(const struct path *, struct file *, const struct cred *);
> +extern struct file *filp_clone_open(struct file *);
>  
>  /*
>   * inode.c
> diff --git a/fs/open.c b/fs/open.c
> index 55bdc75..bb7ffd6 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -1004,6 +1004,26 @@ struct file *file_open_root(struct dentry *dentry, struct vfsmount *mnt,
>  }
>  EXPORT_SYMBOL(file_open_root);
>  
> +struct file *filp_clone_open(struct file *oldfile)
> +{
> +	struct file *file;
> +	int retval;
> +
> +	file = get_empty_filp();
> +	if (IS_ERR(file))
> +		return file;
> +
> +	file->f_flags = oldfile->f_flags;
> +	retval = vfs_open(&oldfile->f_path, file, oldfile->f_cred);
> +	if (retval) {
> +		fput(file);

You likely want put_file instead, although if I read it right this is
only cosmetics for consistency with dentry_open.

Also vast majority of the file uses 'error' instead of 'retval'. Any
reason to deviate here?

> +		return ERR_PTR(retval);
> +	}
> +
> +	return file;
> +}
> +EXPORT_SYMBOL(filp_clone_open);
> +
>  long do_sys_open(int dfd, const char __user *filename, int flags, umode_t mode)
>  {
>  	struct open_flags op;
> -- 
> 2.6.2
> 

-- 
Mateusz Guzik

  parent reply	other threads:[~2016-03-08  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1456428890.2377.2.camel@HansenPartnership.com>
     [not found] ` <1456428890.2377.2.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2016-02-25 19:36   ` [Patch v2 1/3] fs: add filp_clone_open API James Bottomley
2016-02-25 19:37   ` [Patch v2 2/3] binfmt_misc: add persistent opened binary handler for containers James Bottomley
2016-02-25 19:38   ` [Patch v2 3/3] binfmt_misc: add F option description to documentation James Bottomley
     [not found]     ` <1456429136.2377.7.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2016-02-29  5:32       ` Randy Dunlap
     [not found] ` <1456429008.2377.4.camel@HansenPartnership.com>
     [not found]   ` <1456429008.2377.4.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2016-03-08  6:19     ` [Patch v2 1/3] fs: add filp_clone_open API Serge E. Hallyn
2016-03-08  9:17     ` Mateusz Guzik [this message]
2016-03-08 11:19       ` James Bottomley
     [not found] ` <1456429071.2377.5.camel@HansenPartnership.com>
     [not found]   ` <1456429071.2377.5.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2016-03-08  8:10     ` [Patch v2 2/3] binfmt_misc: add persistent opened binary handler for containers Serge E. Hallyn

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=20160308091705.GB2189@mguzik \
    --to=mguzik-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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