From: Mark Salyzyn <salyzyn@android.com>
To: linux-kernel@vger.kernel.org
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Jonathan Corbet <corbet@lwn.net>, Vivek Goyal <vgoyal@redhat.com>,
linux-unionfs@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] overlayfs: caller_credentials option bypass creator_cred
Date: Mon, 18 Jun 2018 12:32:13 -0700 [thread overview]
Message-ID: <afbcabfc-2e25-d2fc-107a-5418b5e0806f@android.com> (raw)
In-Reply-To: <20180618192726.67981-1-salyzyn@android.com>
On 06/18/2018 12:27 PM, Mark Salyzyn wrote:
> All accesses to the lower filesystems reference the creator (mount)
> context. This is a security issue as the user context does not
> overlay the creator context.
<sigh> been typing overlay far too many times, muscle memory struck!
"overlap the creator context."
-- Mark
next prev parent reply other threads:[~2018-06-18 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 19:27 [PATCH v2] overlayfs: caller_credentials option bypass creator_cred Mark Salyzyn
2018-06-18 19:32 ` Mark Salyzyn [this message]
2018-06-18 22:05 ` Eric W. Biederman
2018-06-19 5:39 ` Amir Goldstein
2018-06-19 14:16 ` Vivek Goyal
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=afbcabfc-2e25-d2fc-107a-5418b5e0806f@android.com \
--to=salyzyn@android.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.com \
/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