linux-kernel - Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Aug 2010 22:35:44 +0200
FROM:	Karsten Mehrhoff <kawime@....de>
To:	jkosina@...e.cz,
	"Tetsuo Handa" <penguin-kernel@...ove.sakura.ne.jp>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel
 2.6.35-git2/3

[Am 10.08.2010, 22:14 Uhr, schrieb Tetsuo Handa  
<penguin-kernel@...ove.sakura.ne.jp>]

> Jiri Kosina wrote:
>> Still, if a legacy userspace application is able to cause kernel panic,
>> that sounds like something we'd rather fix immediately.
>
> I assume the panic message which Karsten encountered is either
>
>   Profile version %u is not supported.
>
> or
>
>   Profile %u (used by '%s') not defined.
>
> which happens only if access control rules (a.k.a. policy) was not
> loaded when /sbin/init starts.
>
> If what Karsten encountered is not the cases above,
> I agree that we need to fix immediately.
>
> Regards.

The panic message was:
>   Profile %u (used by '%s') not defined.

Profile 0 (used by '0') not defined.


Regards

Karsten
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/