From: ebiederm@xmission.com (Eric W. Biederman)
To: David Howells <dhowells@redhat.com>
Cc: linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Karel Zak <kzak@redhat.com>,
util-linux@vger.kernel.org, Andy Lutomirski <luto@amacapital.net>
Subject: Re: [RFD] A mount api that notices previous mounts
Date: Wed, 30 Jan 2019 07:24:00 -0600 [thread overview]
Message-ID: <877eemth1r.fsf@xmission.com> (raw)
In-Reply-To: <9151.1548852654@warthog.procyon.org.uk> (David Howells's message of "Wed, 30 Jan 2019 12:50:54 +0000")
David Howells <dhowells@redhat.com> writes:
> You need to rebase on linus/master. A bunch of your patches are obsoleted by
> Al's security changes there.
Before anything is merged definitely.
Al dealt with mount options from the LSMs in a slightly different way
than I did. At a practical level Als version of the changes to the LSMs
and mine are you say po-tae-toe I say po-tah-toe differences so I don't
see that influencing semantics up at the api level.
For purposes of disucssing an API (not of merging one) I chose to start
with code I had a reasonable amount of testing against, so that other
people could play with it without expecting trouble.
Eric
prev parent reply other threads:[~2019-01-30 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:44 [RFD] A mount api that notices previous mounts Eric W. Biederman
2019-01-29 23:01 ` Casey Schaufler
2019-01-30 1:15 ` Eric W. Biederman
2019-01-30 1:23 ` Eric W. Biederman
2019-01-30 12:47 ` Eric W. Biederman
2019-01-30 16:19 ` Casey Schaufler
2019-01-30 12:06 ` Karel Zak
2019-01-30 13:01 ` David Howells
2019-01-30 13:35 ` Eric W. Biederman
2019-01-30 18:00 ` Karel Zak
2019-01-30 17:43 ` Karel Zak
2019-01-30 13:45 ` Eric W. Biederman
2019-01-30 12:50 ` David Howells
2019-01-30 13:24 ` Eric W. Biederman [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=877eemth1r.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=dhowells@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=util-linux@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