From: Alexander Morozov <alexandr.morozov@docker.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alexander Morozov <lk4d4@docker.com>
Subject: [PATCH 2/2] fs/overlay: use same inodes for hardlinks
Date: Fri, 9 Oct 2015 12:34:57 -0700 [thread overview]
Message-ID: <1444419297-16232-3-git-send-email-lk4d4@docker.com> (raw)
In-Reply-To: <1444419297-16232-1-git-send-email-lk4d4@docker.com>
Fix problem with accessing hardlink to unix-socket. unix_find_other
function from net/unix/af_unix.c uses d_backing_inode helper which in
current implementation doesn't return any "backing" inode, but just
dentry->d_inode, so, there from kern_path we have path with dentry from
overlayfs and not underlying file system. Further in code in
unix_find_socket_byinode we looking for unix-socket by inode, but due
overlayfs implementation that inode for hardlink will be different from
original inode of unix-socket.
Now ovl_link doesn't create new inode, but uses old->d_inode for
instantiating new dentry. Not use inc_nlink, because nlink seems to be
correctly propagated from underlying fs where it need.
Signed-off-by: Alexander Morozov <lk4d4@docker.com>
---
fs/overlayfs/dir.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/fs/overlayfs/dir.c b/fs/overlayfs/dir.c
index 487a157..a55c89b 100644
--- a/fs/overlayfs/dir.c
+++ b/fs/overlayfs/dir.c
@@ -164,8 +164,14 @@ static void ovl_dentry_update_instantiate(struct dentry *dentry,
{
ovl_dentry_version_inc(dentry->d_parent);
ovl_dentry_update(dentry, newdentry);
- ovl_copyattr(newdentry->d_inode, inode);
- d_instantiate(dentry, inode);
+ /*
+ * inode == NULL only in case of hardlink
+ * for hardlink dentry will be instantiated in ovl_link
+ */
+ if (inode) {
+ ovl_copyattr(newdentry->d_inode, inode);
+ d_instantiate(dentry, inode);
+ }
}
static int ovl_create_upper(struct dentry *dentry, struct inode *inode,
@@ -390,16 +396,19 @@ static int ovl_create_or_link(struct dentry *dentry, int mode, dev_t rdev,
const char *link, struct dentry *hardlink)
{
int err;
- struct inode *inode;
+ struct inode *inode = NULL;
struct kstat stat = {
.mode = mode,
.rdev = rdev,
};
err = -ENOMEM;
- inode = ovl_new_inode(dentry->d_sb, mode, dentry->d_fsdata);
- if (!inode)
- goto out;
+ /* We don't need inode for hardlink */
+ if (!hardlink) {
+ inode = ovl_new_inode(dentry->d_sb, mode, dentry->d_fsdata);
+ if (!inode)
+ goto out;
+ }
err = ovl_copy_up(dentry->d_parent);
if (err)
@@ -498,6 +507,10 @@ static int ovl_link(struct dentry *old, struct inode *newdir,
upper = ovl_dentry_upper(old);
err = ovl_create_or_link(new, upper->d_inode->i_mode, 0, NULL, upper);
+ if (!err) {
+ ihold(old->d_inode);
+ d_instantiate(new, old->d_inode);
+ }
out_drop_write:
ovl_drop_write(old);
--
2.6.1
next prev parent reply other threads:[~2015-10-09 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 19:34 [PATCH 0/2] Fix hardlinks in overlay Alexander Morozov
2015-10-09 19:34 ` [PATCH 1/2] fs/overlay: move update and instantiate dentry code to function Alexander Morozov
2015-10-09 19:34 ` Alexander Morozov [this message]
2015-11-23 23:23 ` [PATCH 2/2] fs/overlay: use same inodes for hardlinks Alexander Morozov
2016-03-07 10:49 ` [PATCH 0/2] Fix hardlinks in overlay Miklos Szeredi
2016-03-07 17:33 ` Alexander Morozov
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=1444419297-16232-3-git-send-email-lk4d4@docker.com \
--to=alexandr.morozov@docker.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk4d4@docker.com \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®