From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: [GIT PULL] fix overlayfs deadlock in file_remove_privs()
Date: Wed, 3 Aug 2016 18:32:28 +0100 [thread overview]
Message-ID: <20160803173227.GH2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160803163029.GD25404@veci.piliscsaba.szeredi.hu>
On Wed, Aug 03, 2016 at 06:30:29PM +0200, Miklos Szeredi wrote:
> Hi Al,
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git for-viro
>
> This fixes the deadlock introduced by making the suid removal actually work on
> overlayfs.
>
> Responsible commit 07a2daab49c5 ("ovl: Copy up underlying inode's ->i_mode to
> overlay inode") unfortunately slipped through my testing and 4.7 was released
> with this bug.
>
> Two more patches are cleaning away unneeded exports of related helpers.
Pulled, will push tonight.
prev parent reply other threads:[~2016-08-03 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 16:30 [GIT PULL] fix overlayfs deadlock in file_remove_privs() Miklos Szeredi
2016-08-03 17:32 ` Al Viro [this message]
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=20160803173227.GH2356@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.