From: Vivek Goyal <vgoyal@redhat.com>
To: linux-unionfs@vger.kernel.org, miklos@szeredi.hu
Cc: vgoyal@redhat.com, virtio-fs@redhat.com
Subject: [PATCH 1/2] overlayfs: ovl_setattr() should clear ATTR_FILE from attr->ia_valid
Date: Wed, 22 Apr 2020 09:08:49 -0400 [thread overview]
Message-ID: <20200422130850.59900-2-vgoyal@redhat.com> (raw)
In-Reply-To: <20200422130850.59900-1-vgoyal@redhat.com>
ovl_setattr() can be passed an attr which has ATTR_FILE set and
attr->ia_file is a file pointer to overlay file. This is done
in open(O_TRUNC) path.
We should either replace with attr->ia_file with underlying file object
or clear ATTR_FILE so that underlying filesystem does not end up using
overlayfs file object pointer.
There are no good use cases yet so for now clear ATTR_FILE. fuse seems
to be one user which can use this. But it can work even without this.
So it is not mandatory to pass ATTR_FILE to fuse.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
fs/overlayfs/inode.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/fs/overlayfs/inode.c b/fs/overlayfs/inode.c
index b0d42ece4d7c..8d147bc70f0b 100644
--- a/fs/overlayfs/inode.c
+++ b/fs/overlayfs/inode.c
@@ -58,6 +58,11 @@ int ovl_setattr(struct dentry *dentry, struct iattr *attr)
if (attr->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID))
attr->ia_valid &= ~ATTR_MODE;
+ /* We might have to translate ovl file into underlying file
+ * object once some use cases are there. For now, simply
+ * don't let underlying filesystem rely on attr->ia_file */
+ attr->ia_valid &= ~ATTR_FILE;
+
inode_lock(upperdentry->d_inode);
old_cred = ovl_override_creds(dentry->d_sb);
err = notify_change(upperdentry, attr, NULL);
--
2.25.3
next prev parent reply other threads:[~2020-04-22 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 13:08 [PATCH 0/2] overlayfs: Fix overlayfs on virtiofs open(O_TRUNC) issue Vivek Goyal
2020-04-22 13:08 ` Vivek Goyal [this message]
2020-04-22 13:08 ` [PATCH 2/2] overlayfs: ovl_setattr() should clear ATTR_OPEN Vivek Goyal
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=20200422130850.59900-2-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=virtio-fs@redhat.com \
/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