From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs fixes for 5.11-rc7
Date: Thu, 4 Feb 2021 10:19:43 +0100 [thread overview]
Message-ID: <20210204091943.GA1208880@miu.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git tags/ovl-fixes-5.11-rc7
- Fix capability conversion and minor overlayfs bugs that are related to
the unprivileged overlay mounts introduced in this cycle.
- Fix two recent (v5.10) and one old (v4.10) bug.
- Clean up security xattr copy-up (related to a SELinux regression).
Thanks,
Miklos
---
Amir Goldstein (1):
ovl: skip getxattr of security labels
Liangyan (1):
ovl: fix dentry leak in ovl_get_redirect
Miklos Szeredi (4):
ovl: add warning on user_ns mismatch
ovl: perform vfs_getxattr() with mounter creds
cap: fix conversions on getxattr
ovl: avoid deadlock on directory ioctl
Sargun Dhillon (1):
ovl: implement volatile-specific fsync error behaviour
---
Documentation/filesystems/overlayfs.rst | 8 ++++
fs/overlayfs/copy_up.c | 15 ++++----
fs/overlayfs/dir.c | 2 +-
fs/overlayfs/file.c | 5 ++-
fs/overlayfs/inode.c | 2 +
fs/overlayfs/overlayfs.h | 1 +
fs/overlayfs/ovl_entry.h | 2 +
fs/overlayfs/readdir.c | 28 +++++---------
fs/overlayfs/super.c | 38 +++++++++++++++----
fs/overlayfs/util.c | 27 +++++++++++++
security/commoncap.c | 67 +++++++++++++++++++++------------
11 files changed, 136 insertions(+), 59 deletions(-)
next reply other threads:[~2021-02-04 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 9:19 Miklos Szeredi [this message]
2021-02-04 18:10 ` [GIT PULL] overlayfs fixes for 5.11-rc7 pr-tracker-bot
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=20210204091943.GA1208880@miu.piliscsaba.redhat.com \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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).