linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 4.19-rc4
Date: Thu, 13 Sep 2018 20:30:30 +0200	[thread overview]
Message-ID: <20180913183030.GB23439@veci.piliscsaba.redhat.com> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git tags/ovl-fixes-4.19-rc4

This fixes a regression in the recent file stacking update, reported and fixed
by Amir Goldstein.  The fix is fairly trivial, but involves adding a fadvise()
f_op and the associated churn in the vfs.  As discussed on -fsdevel, there are
other possible uses for this method, than allowing proper stacking for overlays.

And there's one other fix for a syzkaller detected oops.

Thanks,
Miklos

---
Amir Goldstein (6):
      ovl: respect FIEMAP_FLAG_SYNC flag
      ovl: fix GPF in swapfile_activate of file from overlayfs over xfs
      Documentation/filesystems: update documentation of file_operations
      vfs: add the fadvise() file operation
      vfs: implement readahead(2) using POSIX_FADV_WILLNEED
      ovl: add ovl_fadvise()

Miklos Szeredi (1):
      ovl: fix oopses in ovl_fill_super() failure paths

---
 Documentation/filesystems/vfs.txt | 21 +++++++++-
 fs/overlayfs/file.c               | 23 +++++++++--
 fs/overlayfs/inode.c              | 10 +++++
 fs/overlayfs/super.c              | 26 +++++++------
 include/linux/fs.h                |  5 +++
 mm/Makefile                       |  3 +-
 mm/fadvise.c                      | 81 +++++++++++++++++++++++----------------
 mm/readahead.c                    | 45 ++++++++--------------
 8 files changed, 134 insertions(+), 80 deletions(-)

                 reply	other threads:[~2018-09-13 18:30 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=20180913183030.GB23439@veci.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).