From: <gregkh@linuxfoundation.org>
To: koct9i@gmail.com, gregkh@linuxfoundation.org, miklos@szeredi.hu
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "ovl: copy new uid/gid into overlayfs runtime inode" has been added to the 4.4-stable tree
Date: Sat, 12 Mar 2016 19:47:40 -0800 [thread overview]
Message-ID: <14578408605728@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
ovl: copy new uid/gid into overlayfs runtime inode
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ovl-copy-new-uid-gid-into-overlayfs-runtime-inode.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From b81de061fa59f17d2730aabb1b84419ef3913810 Mon Sep 17 00:00:00 2001
From: Konstantin Khlebnikov <koct9i@gmail.com>
Date: Sun, 31 Jan 2016 16:21:29 +0300
Subject: ovl: copy new uid/gid into overlayfs runtime inode
From: Konstantin Khlebnikov <koct9i@gmail.com>
commit b81de061fa59f17d2730aabb1b84419ef3913810 upstream.
Overlayfs must update uid/gid after chown, otherwise functions
like inode_owner_or_capable() will check user against stale uid.
Catched by xfstests generic/087, it chowns file and calls utimes.
Signed-off-by: Konstantin Khlebnikov <koct9i@gmail.com>
Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/overlayfs/inode.c | 2 ++
1 file changed, 2 insertions(+)
--- a/fs/overlayfs/inode.c
+++ b/fs/overlayfs/inode.c
@@ -65,6 +65,8 @@ int ovl_setattr(struct dentry *dentry, s
mutex_lock(&upperdentry->d_inode->i_mutex);
err = notify_change(upperdentry, attr, NULL);
+ if (!err)
+ ovl_copyattr(upperdentry->d_inode, dentry->d_inode);
mutex_unlock(&upperdentry->d_inode->i_mutex);
}
ovl_drop_write(dentry);
Patches currently in stable-queue which might be from koct9i@gmail.com are
queue-4.4/ovl-ignore-lower-entries-when-checking-purity-of-non-directory-entries.patch
queue-4.4/ovl-copy-new-uid-gid-into-overlayfs-runtime-inode.patch
queue-4.4/ovl-fix-working-on-distributed-fs-as-lower-layer.patch
queue-4.4/ovl-fix-getcwd-failure-after-unsuccessful-rmdir.patch
reply other threads:[~2016-03-13 3:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14578408605728@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=koct9i@gmail.com \
--cc=miklos@szeredi.hu \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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).