linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-fsdevel@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
	Christian Brauner <christian@brauner.io>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Miklos Szeredi <miklos@szeredi.hu>,
	lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM/BPF Topic] Lets have the Interface debate: configfd vs fsconfig
Date: Sat, 15 Feb 2020 10:44:57 -0500	[thread overview]
Message-ID: <1581781497.3847.5.camel@HansenPartnership.com> (raw)

I've made the case in email that interfaces should always be as general
as they can be.  The counter argument is that interfaces which are too
general can be too powerful and hard for containment logic, like
seccomp, to properly constrain and predict the outcomes from the
various parameters.  So lets have that debate.  My argument is that
essentially we're good enough to handle the power wisely and we can
design interfaces, like configfd, to have easy introspection properties
for confinement tools, and I'm happy to debate this with anyone on the
less power makes easier interfaces side.

James


                 reply	other threads:[~2020-02-15 15:45 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=1581781497.3847.5.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=christian@brauner.io \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=miklos@szeredi.hu \
    --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).