linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-unionfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/7] vfs: export filp_clone_open()
Date: Thu, 24 Nov 2016 11:55:39 +0100	[thread overview]
Message-ID: <1479984944-1017-4-git-send-email-mszeredi@redhat.com> (raw)
In-Reply-To: <1479984944-1017-1-git-send-email-mszeredi@redhat.com>

Already exported to modules, just needs to move declaration from
"fs/internal.h" to <linux/fs.h>.

This will be used by overlayfs to clone a read-only file that has been
copied up after being opened.  The clone will refer to the copied-up uppper
file instead of the original, lower file.

Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
---
 fs/internal.h      | 1 -
 include/linux/fs.h | 1 +
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/internal.h b/fs/internal.h
index f4da3341b4a3..361ba1c12698 100644
--- a/fs/internal.h
+++ b/fs/internal.h
@@ -112,7 +112,6 @@ 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/include/linux/fs.h b/include/linux/fs.h
index 87a32f999812..e3bc970214e1 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -2355,6 +2355,7 @@ extern struct file *filp_open(const char *, int, umode_t);
 extern struct file *file_open_root(struct dentry *, struct vfsmount *,
 				   const char *, int, umode_t);
 extern struct file * dentry_open(const struct path *, int, const struct cred *);
+extern struct file *filp_clone_open(struct file *);
 extern int filp_close(struct file *, fl_owner_t id);
 
 extern struct filename *getname_flags(const char __user *, int, int *);
-- 
2.5.5


  parent reply	other threads:[~2016-11-24 11:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 10:55 [PATCH 0/7] overlayfs: fix ro/rw fd data inconsistecies Miklos Szeredi
2016-11-24 10:55 ` Miklos Szeredi
2016-11-24 14:14   ` Miklos Szeredi
2016-11-24 20:50     ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 1/7] vfs: allow overlayfs to intercept file ops Miklos Szeredi
2016-11-24 10:55 ` Miklos Szeredi [this message]
2016-11-24 10:55 ` [PATCH 3/7] mm: ovl: copy-up on MAP_SHARED Miklos Szeredi
2016-11-25 21:20   ` [mm] 68ab21008a: BUG:unable_to_handle_kernel kernel test robot
2016-11-24 10:55 ` [PATCH 4/7] ovl: add infrastructure for intercepting file ops Miklos Szeredi
2016-11-24 11:52   ` Amir Goldstein
2016-11-24 12:03     ` Miklos Szeredi
2016-11-24 13:12       ` Amir Goldstein
2016-11-24 13:51         ` Miklos Szeredi
2016-11-24 14:08           ` Amir Goldstein
2016-11-25  5:22             ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 5/7] ovl: intercept read_iter Miklos Szeredi
2016-11-24 10:55 ` [PATCH 6/7] ovl: intercept mmap Miklos Szeredi
2016-11-24 13:25   ` Amir Goldstein
2016-11-24 18:03     ` Amir Goldstein
2016-11-24 19:06       ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 7/7] ovl: intercept fsync Miklos Szeredi

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=1479984944-1017-4-git-send-email-mszeredi@redhat.com \
    --to=mszeredi@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@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).