mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
	takedakn@nttdata.co.jp, lists@nerdbynature.de, kawime@gmx.de,
	jkosina@suse.cz, linux-security-module@vger.kernel.org
Subject: Re: 2.6.36-rc7: kernel panic with SECURITY_TOMOYO=y
Date: Fri,  8 Oct 2010 15:30:52 +0900 (JST)	[thread overview]
Message-ID: <20101008153001.BCE5.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <201010080626.o986QJX4002281@www262.sakura.ne.jp>

> From cc7601c18982909987bbb48971acb86a69a3317a Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Fri, 8 Oct 2010 14:43:22 +0900
> Subject: [PATCH] TOMOYO: Print URL information before panic().
> 
> Configuration files for TOMOYO 2.3 are not compatible with TOMOYO 2.2.
> But current panic() message is too unfriendly and is confusing users.
> 
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
>  security/tomoyo/common.c |   11 ++++++++++-
>  1 files changed, 10 insertions(+), 1 deletions(-)
> 
> diff --git a/security/tomoyo/common.c b/security/tomoyo/common.c
> index c668b44..1f0d45a 100644
> --- a/security/tomoyo/common.c
> +++ b/security/tomoyo/common.c
> @@ -2051,13 +2051,22 @@ void tomoyo_check_profile(void)
>  		const u8 profile = domain->profile;
>  		if (tomoyo_profile_ptr[profile])
>  			continue;
> +		printk(KERN_ERR "You need to define profile %u before using it.\n",
> +		       profile);
> +		printk(KERN_ERR "Please see http://tomoyo.sourceforge.jp/2.3/ "
> +		       "for more information.\n");
>  		panic("Profile %u (used by '%s') not defined.\n",
>  		      profile, domain->domainname->name);
>  	}
>  	tomoyo_read_unlock(idx);
> -	if (tomoyo_profile_version != 20090903)
> +	if (tomoyo_profile_version != 20090903) {
> +		printk(KERN_ERR "You need to install userland programs for "
> +		       "TOMOYO 2.3 and initialize policy configuration.\n");
> +		printk(KERN_ERR "Please see http://tomoyo.sourceforge.jp/2.3/ "
> +		       "for more information.\n");
>  		panic("Profile version %u is not supported.\n",
>  		      tomoyo_profile_version);
> +	}
>  	printk(KERN_INFO "TOMOYO: 2.3.0\n");
>  	printk(KERN_INFO "Mandatory Access Control activated.\n");
>  }
> -- 
> 1.7.1


Looks good to me. thanks.
	Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>



  reply	other threads:[~2010-10-08  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 22:43 Christian Kujau
2010-10-07 23:57 ` Christian Kujau
2010-10-08  0:10   ` Tetsuo Handa
2010-10-08  0:19     ` lists
2010-10-08  4:55   ` KOSAKI Motohiro
2010-10-08  6:26     ` Tetsuo Handa
2010-10-08  6:30       ` KOSAKI Motohiro [this message]
2010-10-08  8:47       ` 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=20101008153001.BCE5.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=jkosina@suse.cz \
    --cc=kawime@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --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

all inboxes | Powered by JetHome®