linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfs: update atime using file->f_inode
Date: Thu, 17 Mar 2016 17:36:30 +0100	[thread overview]
Message-ID: <20160317163630.GR8655@tucsk> (raw)
In-Reply-To: <145424638614.10446.16013603987277558993.stgit@zurg>

On Sun, Jan 31, 2016 at 04:19:46PM +0300, Konstantin Khlebnikov wrote:
> This fixes some cases of missing atime update for overlayfs.

Problem is it will update atime on lower layer, even if it's explicitly marked
read-only.  Which I think is a pretty bad breakage of assumptions.

The following patch updates atime (untested) but only in the upper layer.
Obviously it makes no sense to copy-up due to an atime update.

Thanks,
Miklos
---
 fs/overlayfs/inode.c |   22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

--- a/fs/overlayfs/inode.c
+++ b/fs/overlayfs/inode.c
@@ -370,6 +370,27 @@ struct inode *ovl_d_select_inode(struct
 	return d_backing_inode(realpath.dentry);
 }
 
+static int ovl_update_time(struct inode *inode, struct timespec *ts, int flags)
+{
+	struct dentry *alias;
+	struct path upperpath;
+
+	if (!(flags & S_ATIME))
+		return 0;
+
+	alias = d_find_any_alias(inode);
+	if (!alias)
+		return 0;
+
+	ovl_path_upper(alias, &upperpath);
+	if (!upperpath.dentry)
+		return 0;
+
+	touch_atime(&upperpath);
+
+	return 0;
+}
+
 static const struct inode_operations ovl_file_inode_operations = {
 	.setattr	= ovl_setattr,
 	.permission	= ovl_permission,
@@ -378,6 +399,7 @@ static const struct inode_operations ovl
 	.getxattr	= ovl_getxattr,
 	.listxattr	= ovl_listxattr,
 	.removexattr	= ovl_removexattr,
+	.update_time	= ovl_update_time,
 };
 
 static const struct inode_operations ovl_symlink_inode_operations = {

      reply	other threads:[~2016-03-17 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 13:19 [PATCH] vfs: update atime using file->f_inode Konstantin Khlebnikov
2016-03-17 16:36 ` Miklos Szeredi [this message]

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=20160317163630.GR8655@tucsk \
    --to=miklos@szeredi.hu \
    --cc=koct9i@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --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 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).