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.8-rc6
Date: Fri, 17 Jul 2020 13:55:30 +0200 [thread overview]
Message-ID: <20200717115237.GD6171@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.8-rc6
Fix the following:
- a regression introduced in v4.20 in handling a regenerated squashfs
lower layer
- two regressions in this cycle, one of which is Oops inducing
- miscellaneous issues.
Thanks,
Miklos
----------------------------------------------------------------
Amir Goldstein (7):
ovl: relax WARN_ON() when decoding lower directory file handle
ovl: fix oops in ovl_indexdir_cleanup() with nfs_export=on
ovl: fix regression with re-formatted lower squashfs
ovl: force read-only sb on failure to create index dir
ovl: fix mount option checks for nfs_export with no upperdir
ovl: fix unneeded call to ovl_change_flags()
ovl: fix lookup of indexed hardlinks with metacopy
youngjun (3):
ovl: inode reference leak in ovl_is_inuse true case.
ovl: change ovl_copy_up_flags static
ovl: remove not used argument in ovl_check_origin
---
Documentation/filesystems/overlayfs.rst | 4 +-
fs/overlayfs/copy_up.c | 2 +-
fs/overlayfs/export.c | 2 +-
fs/overlayfs/file.c | 10 +++--
fs/overlayfs/namei.c | 15 +++----
fs/overlayfs/overlayfs.h | 1 -
fs/overlayfs/super.c | 73 ++++++++++++++++++++++-----------
7 files changed, 65 insertions(+), 42 deletions(-)
next reply other threads:[~2020-07-17 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 11:55 Miklos Szeredi [this message]
2020-07-17 17:40 ` [GIT PULL] overlayfs fixes for 5.8-rc6 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=20200717115237.GD6171@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).