linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: [PATCH 0/3] overlayfs: vfs fixes
Date: Tue,  5 Sep 2017 09:46:33 +0200	[thread overview]
Message-ID: <1504597596-17994-1-git-send-email-mszeredi@redhat.com> (raw)

Following patches fix overlayfs bugs.  The patches impact vfs code, so
posting for review to a wider audience.

They can also be found on the overlayfs-next branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next

Hoping to get these bugfixes into 4.14.

Thanks,
Miklos
---

Miklos Szeredi (3):
  vfs: add flags to d_real()
  ovl: fix relatime for directories
  ovl: don't allow writing ioctl on lower layer

 Documentation/filesystems/Locking |  2 +-
 Documentation/filesystems/vfs.txt |  2 +-
 fs/inode.c                        |  3 +-
 fs/internal.h                     |  2 ++
 fs/namespace.c                    | 64 +++++++++++++++++++++++++++++++++++++--
 fs/open.c                         |  8 ++---
 fs/overlayfs/super.c              | 10 ++++--
 fs/xattr.c                        |  9 +++---
 include/linux/dcache.h            | 15 ++++++---
 include/linux/fs.h                |  2 +-
 10 files changed, 95 insertions(+), 22 deletions(-)

-- 
2.5.5

             reply	other threads:[~2017-09-05  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  7:46 Miklos Szeredi [this message]
2017-09-05  7:46 ` [PATCH 1/3] vfs: add flags to d_real() Miklos Szeredi
2017-09-05  8:55   ` Amir Goldstein
2017-09-05  9:02     ` Miklos Szeredi
2017-09-05  7:46 ` [PATCH 2/3] ovl: fix relatime for directories Miklos Szeredi
2017-09-05 12:53   ` Miklos Szeredi
2017-09-05  7:46 ` [PATCH 3/3] ovl: don't allow writing ioctl on lower layer 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=1504597596-17994-1-git-send-email-mszeredi@redhat.com \
    --to=mszeredi@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --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).