public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshiharu Harada <haradats@nttdata.co.jp>
To: Pavel Machek <pavel@ucw.cz>
Cc: 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: Mon, 23 Feb 2009 16:37:02 +0900	[thread overview]
Message-ID: <49A2521E.5030805@nttdata.co.jp> (raw)
In-Reply-To: <20090222144811.GJ1586@ucw.cz>

Pavel Machek wrote:
> On Sun 2009-02-22 23:27:34, Tetsuo Handa wrote:
>> Pavel Machek wrote:
>>> On Thu 2009-02-12 16:34:16, James Morris wrote:
>>>> On Thu, 5 Feb 2009, Kentaro Takeda wrote:
>>>>
>>>>> TOMOYO Linux is a name-based MAC extension (LSM module) for the Linux kernel.
>>>>>
>>>> Applied to 
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
>>>>
>>> Does that mean tomoyo is scheduled for 2.6.30?
>>>
>> TOMOYO is already in linux-next tree and ready to go into 2.6.30 .
> 
> Last time I looked it included script parser and some
> interpretter... Was that solved?
> 									Pavel

Are you talking about the interface between
userland and kernel regarding string data?

Linus once said in a Smack thread (http://lkml.org/lkml/2007/11/5/129) 
>> On Sun, Nov 04, 2007 at 12:28:48PM +0000, Pavel Machek wrote:
>> > Can we avoid string parsers in the kernel?
>> 
>> Ok, Could someone suggest a better idea please ?. 
>
> I personally think string parsers are *much* better than the alternatives 
> (which basically boil down to nasty binary interfaces)
>
>> I thought about packing the rules in a structure and sending
>> it over an ioctl() command. Is this applicable ?
>
> That's *MUCH* worse.
>
> Strings are nice. They aren't that complex, and as long as it's not a 
> performance-critical area, there are basically no downsides.
>
> Binary structures and ioctl's are *much* worse. They are totally 
> undebuggable with generic tools (think "echo" or "strace"), and they are a 
> total nightmare to parse across architectures and pointer sizes.
>
> So the rule should be: always use strings if at all possible and relevant.
> If the data is fundamentally binary, it shouldn't be re-coded to ascii
> (no real advantage), but if the data is "stringish", and there aren't
> big performance issues, then keep it as strings.

Admiring your concern, I would like to follow the above directions.

Best regards,
Toshiharu Harada


  reply	other threads:[~2009-02-23  8:13 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 [this message]
2009-02-25 19:46           ` Pavel Machek
2009-02-27  1:27             ` KOSAKI Motohiro
2009-03-01 22:45               ` Pavel Machek

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=49A2521E.5030805@nttdata.co.jp \
    --to=haradats@nttdata.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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