From: Pavel Machek <pavel@ucw.cz>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: private user<->kernel interface in linux-2.6.30, was Re: TOMOYO in linux-next
Date: Fri, 27 Mar 2009 12:41:48 +0100 [thread overview]
Message-ID: <20090327114148.GE2585@elf.ucw.cz> (raw)
In-Reply-To: <200903270412.n2R4CG7o054009@www262.sakura.ne.jp>
Hi!
> > That's my main complaint: Documentation.*tomoyo nor
> > Documentation.*TOMOYO does not exist, still this adds a *lot* of new
> > user<->kernel interfaces.
> >
> > New user<->kernel interaces should be documented and very carefuly
> > reviewed; I don't think that happened here.
> These user<->kernel interface are for TOMOYO's policy management tools,
> not for general userland applications like /bin/bash /usr/sbin/sshd etc.
I do believe all user<->kernel interfaces should be properly
reviewed/documented. We'll have to maintain them forever. Just because
you don't intend them to be used by /bin/bash does not mean people
will not use them; and it does not mean we will not have to carry them
forever.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-03-27 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 21:50 Pavel Machek
2009-03-27 0:15 ` James Morris
2009-03-27 0:30 ` Pavel Machek
2009-03-27 0:51 ` James Morris
2009-03-27 11:36 ` Pavel Machek
2009-03-27 0:36 ` Pavel Machek
2009-03-27 0:46 ` James Morris
2009-03-27 11:35 ` Pavel Machek
2009-03-27 4:12 ` Tetsuo Handa
2009-03-27 8:04 ` James Morris
2009-03-27 11:40 ` Pavel Machek
2009-03-27 11:41 ` Pavel Machek [this message]
2009-04-06 11:49 ` Tetsuo Handa
2009-04-06 12:01 ` Pavel Machek
2009-04-06 22:21 ` James Morris
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=20090327114148.GE2585@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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
all inboxes | Powered by JetHome®