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.1
Date: Tue, 26 May 2015 18:02:55 +0200 [thread overview]
Message-ID: <20150526160255.GC4531@tucsk.suse.de> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
Overlayfs rmdir() failed to check for emptiness in one case; this was introduced
in 4.0. The other bug was there since day one: failure to mount if upper fs is
full, which bit some OpenWRT folks.
Thanks,
Miklos
---
Miklos Szeredi (2):
ovl: don't remove non-empty opaque directory
ovl: mount read-only if workdir can't be created
---
fs/overlayfs/copy_up.c | 3 +++
fs/overlayfs/dir.c | 33 ++++++++++++++++++++++++++++-----
fs/overlayfs/super.c | 10 +++++-----
3 files changed, 36 insertions(+), 10 deletions(-)
reply other threads:[~2015-05-26 16:00 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=20150526160255.GC4531@tucsk.suse.de \
--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