From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] Assorted overlayfs fixes for 4.19-rc5
Date: Tue, 18 Sep 2018 16:34:30 +0300 [thread overview]
Message-ID: <20180918133434.27437-1-amir73il@gmail.com> (raw)
Miklos,
Found one memory leak that needs a fix for stable and
two missing freeze protections in stacked f_ops.
Last patch is not a bugfix, but it fixes a trap that we set
for developers back in v4.10 - and you happened to step into.
The series passed xfstests -g quick with overlayfs over
xfs and ext4 and the usual unionmount testsuite torture.
The memory leak was detected with tests overlay/051,053
after I enabled kmemleak on my test setup.
Thanks,
Amir.
Amir Goldstein (4):
ovl: fix memory leak on unlink of indexed file
ovl: fix freeze protection bypass in ovl_write_iter()
ovl: fix freeze protection bypass in ovl_clone_file_range()
vfs: swap names of {do,vfs}_clone_file_range()
fs/ioctl.c | 2 +-
fs/nfsd/vfs.c | 3 ++-
fs/overlayfs/copy_up.c | 2 +-
fs/overlayfs/file.c | 2 ++
fs/overlayfs/util.c | 3 ++-
fs/read_write.c | 17 +++++++++++++++--
include/linux/fs.h | 17 +++--------------
7 files changed, 26 insertions(+), 20 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-18 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 13:34 Amir Goldstein [this message]
2018-09-18 13:34 ` [PATCH 1/4] ovl: fix memory leak on unlink of indexed file Amir Goldstein
2018-09-18 13:59 ` Greg KH
2018-09-18 15:14 ` Amir Goldstein
2018-09-18 13:34 ` [PATCH 2/4] ovl: fix freeze protection bypass in ovl_write_iter() Amir Goldstein
2018-09-18 13:34 ` [PATCH 3/4] ovl: fix freeze protection bypass in ovl_clone_file_range() Amir Goldstein
2018-09-18 13:34 ` [PATCH 4/4] vfs: swap names of {do,vfs}_clone_file_range() Amir Goldstein
2018-09-24 8:25 ` [PATCH 0/4] Assorted overlayfs fixes for 4.19-rc5 Amir Goldstein
2018-09-24 8:56 ` Miklos Szeredi
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=20180918133434.27437-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).