From: Zhang AiHua <zhangaihua1@huawei.com>
To: Miklos Szeredi <miklos@szeredi.hu>, linux-unionfs@vger.kernel.org
Subject: Re: retry: [PATCH] ovl: fix inode in utimes_common on overlayfs.
Date: Thu, 11 Aug 2016 17:13:54 +0800 [thread overview]
Message-ID: <57AC41D2.1030902@huawei.com> (raw)
In-Reply-To: <20160810080116.GF25404@veci.piliscsaba.szeredi.hu>
Hi,
I have tested this patch, it's ok and looks better, thanks.
--AiHua
在 2016/8/10 16:01, Miklos Szeredi 写道:
> On Tue, Aug 09, 2016 at 11:00:03AM +0800, Zhang AiHua wrote:
>
>> From: Aihua Zhang <zhangaihua1@huawei.com>
>>
>> the check IS_IMMUTABLE(inode) is invalid in utimes_commmon,
>> the inode should point to upper rather than merge.
>>
>> the patch also fix the error in LTP(utimensat01).
>>
>> Signed-off-by: Aihua Zhang <zhangaihua1@huawei.com>
>
> Can you please try this alternative patch?
>
> Thanks,
> Miklos
>
> ---
> fs/attr.c | 15 +++++++++++++++
> fs/utimes.c | 17 +----------------
> include/linux/fs.h | 1 +
> 3 files changed, 17 insertions(+), 16 deletions(-)
>
> --- a/fs/attr.c
> +++ b/fs/attr.c
> @@ -202,6 +202,21 @@ int notify_change(struct dentry * dentry
> return -EPERM;
> }
>
> + /*
> + * If utimes(2) and friends are called with times == NULL (or both
> + * times are UTIME_NOW), then we need to check for write permission
> + */
> + if (ia_valid & ATTR_TOUCH) {
> + if (IS_IMMUTABLE(inode))
> + return -EPERM;
> +
> + if (!inode_owner_or_capable(inode)) {
> + error = inode_permission(inode, MAY_WRITE);
> + if (error)
> + return error;
> + }
> + }
> +
> if ((ia_valid & ATTR_MODE)) {
> umode_t amode = attr->ia_mode;
> /* Flag setting protected by i_mutex */
> --- a/fs/utimes.c
> +++ b/fs/utimes.c
> @@ -87,21 +87,7 @@ static int utimes_common(struct path *pa
> */
> newattrs.ia_valid |= ATTR_TIMES_SET;
> } else {
> - /*
> - * If times is NULL (or both times are UTIME_NOW),
> - * then we need to check permissions, because
> - * inode_change_ok() won't do it.
> - */
> - error = -EPERM;
> - if (IS_IMMUTABLE(inode))
> - goto mnt_drop_write_and_out;
> -
> - error = -EACCES;
> - if (!inode_owner_or_capable(inode)) {
> - error = inode_permission(inode, MAY_WRITE);
> - if (error)
> - goto mnt_drop_write_and_out;
> - }
> + newattrs.ia_valid |= ATTR_TOUCH;
> }
> retry_deleg:
> inode_lock(inode);
> @@ -113,7 +99,6 @@ static int utimes_common(struct path *pa
> goto retry_deleg;
> }
>
> -mnt_drop_write_and_out:
> mnt_drop_write(path->mnt);
> out:
> return error;
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -224,6 +224,7 @@ typedef int (dio_iodone_t)(struct kiocb
> #define ATTR_KILL_PRIV (1 << 14)
> #define ATTR_OPEN (1 << 15) /* Truncating from open(O_TRUNC) */
> #define ATTR_TIMES_SET (1 << 16)
> +#define ATTR_TOUCH (1 << 17)
>
> /*
> * Whiteout is represented by a char device. The following constants define the
>
> .
>
prev parent reply other threads:[~2016-08-11 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 8:06 [PATCH] ovl: fix inode in utimes_common on overlayfs zhangaihua1
2016-08-09 3:00 ` retry: " Zhang AiHua
2016-08-10 8:01 ` Miklos Szeredi
2016-08-11 9:13 ` Zhang AiHua [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=57AC41D2.1030902@huawei.com \
--to=zhangaihua1@huawei.com \
--cc=linux-unionfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).