From: Pavel Machek <pavel@ucw.cz>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Toshiharu Harada <haradats@nttdata.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
jmorris@namei.org, takedakn@nttdata.co.jp,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [TOMOYO #15 0/8] TOMOYO Linux
Date: Sun, 1 Mar 2009 23:45:49 +0100 [thread overview]
Message-ID: <20090301224549.GC1961@elf.ucw.cz> (raw)
In-Reply-To: <20090227100350.1515.A69D9226@jp.fujitsu.com>
Hi!
> > Yes. maybe ioctl() is worse, but I don't think c-like language parser
> > in kernel is acceptable.
>
> for just clarification to me.
>
> IIUC, many developers said UNNECESSARY parser is BAD (yes, I also think so),
> but nobody said any parser is bad.
>
> Therefore, I think point is that the patch have enough reasonable reason or not.
> and, I thought "pavel, good job. you're right" at you oppositing time because
> tomoyo did't explain any reason at that time.
>
> However, they changed. the patch description of the "[TOMOYO #15 3/8] Common functions for TOMOYO Linux."
> explain the reason.
> for me, I feel it's reasonable reason. then I didn't oppose current tomoyo posting.
>
> So, I don't understand which you oppose
> (1) ANY parser is bad.
> (2) current description still don't explain enough reason.
>
> May I ask you?
I'm not sure if I've seen all the TOMOYO patches... But from what I've
seen of TOMOYO design, putting the parser into kernel was "just
because"; it did not have any good reason. I hate to say that, but
AppArmor was better designed there.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-03-01 22:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:18 [TOMOYO #15 0/8] TOMOYO Linux Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 1/8] Add in_execve flag into task_struct Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 2/8] Memory and pathname management functions Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 3/8] Common functions for TOMOYO Linux Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 4/8] File operation restriction part Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 5/8] Domain transition handler Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 6/8] LSM adapter functions Kentaro Takeda
2009-02-05 17:10 ` Alexey Dobriyan
2009-02-06 1:41 ` Tetsuo Handa
2009-02-05 8:18 ` [TOMOYO #15 7/8] Kconfig and Makefile Kentaro Takeda
2009-02-05 8:18 ` [TOMOYO #15 8/8] MAINTAINERS info Kentaro Takeda
2009-02-12 5:34 ` [TOMOYO #15 0/8] TOMOYO Linux James Morris
2009-02-12 6:53 ` Tetsuo Handa
2009-02-12 9:25 ` James Morris
2009-02-13 7:00 ` Tetsuo Handa
2009-02-14 1:33 ` James Morris
2009-02-22 14:23 ` Pavel Machek
2009-02-22 14:27 ` Tetsuo Handa
2009-02-22 14:48 ` Pavel Machek
2009-02-23 7:37 ` Toshiharu Harada
2009-02-25 19:46 ` Pavel Machek
2009-02-27 1:27 ` KOSAKI Motohiro
2009-03-01 22:45 ` Pavel Machek [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=20090301224549.GC1961@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=haradats@nttdata.co.jp \
--cc=jmorris@namei.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=takedakn@nttdata.co.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