All of lore.kernel.org
 help / color / mirror / Atom feed
* tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
@ 2010-08-06 16:23 Karsten Mehrhoff
  2010-08-07  5:04 ` Tetsuo Handa
  0 siblings, 1 reply; 6+ messages in thread
From: Karsten Mehrhoff @ 2010-08-06 16:23 UTC (permalink / raw)
  To: linux-kernel

Hi, i just compiled the 2.6.35-git3 kernel on my computer using debian 64  
bit as i did with all other kernels before.
Booting the git2/3 kernel results in a kernel panic because of  
/sbin/tomoyo-init.

No problem with the 2.6.35 kernel.

I've to remane /sbin/tomoyo-init to boot the kernel.
Now i purged tomoyo-tools version 2.2.0-20100225 (aptitude purge  
tomoyo-tool) and everything works ok.
Sorry, i forgot to backup the tomoyo-init script.

$ uname -a
Linux xxxxxx 2.6.35-git3 #4 SMP Fri Aug 6 15:22:08 CEST 2010 x86_64  
GNU/Linux


Karsten

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
  2010-08-06 16:23 tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3 Karsten Mehrhoff
@ 2010-08-07  5:04 ` Tetsuo Handa
  2010-08-10 12:44   ` Jiri Kosina
  0 siblings, 1 reply; 6+ messages in thread
From: Tetsuo Handa @ 2010-08-07  5:04 UTC (permalink / raw)
  To: kawime; +Cc: linux-kernel

Hello.

Karsten Mehrhoff wrote:
> Hi, i just compiled the 2.6.35-git3 kernel on my computer using debian 64 bit
> as i did with all other kernels before.
> Booting the git2/3 kernel results in a kernel panic because of
> /sbin/tomoyo-init.
> 
> No problem with the 2.6.35 kernel.
> 
> I've to remane /sbin/tomoyo-init to boot the kernel.
> Now i purged tomoyo-tools version 2.2.0-20100225 (aptitude purge tomoyo-tool) and everything works ok.
> Sorry, i forgot to backup the tomoyo-init script.
> 
> $ uname -a
> Linux xxxxxx 2.6.35-git3 #4 SMP Fri Aug 6 15:22:08 CEST 2010 x86_64 GNU/Linux

Thank you for using TOMOYO. TOMOYO has changed a lot in 2.6.36. Therefore,
you need to upgrade tomoyo-tools package. I'm testing it now.
You can upgrade it by doing

# wget -O tomoyo-tools.tar.gz 'http://sourceforge.jp/projects/tomoyo/svn/view/trunk/2.3.x/tomoyo-tools.tar.gz?root=tomoyo&view=tar'
# tar -zxf tomoyo-tools.tar.gz
# make -C tomoyo-tools/ install

Then, please delete (or rename) /etc/tomoyo/ directory and run
/usr/lib/tomoyo/init_policy .

Please see http://tomoyo.sourceforge.jp/2.3/ for more information.

Thank you.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
  2010-08-07  5:04 ` Tetsuo Handa
@ 2010-08-10 12:44   ` Jiri Kosina
  2010-08-10 20:14     ` Tetsuo Handa
  0 siblings, 1 reply; 6+ messages in thread
From: Jiri Kosina @ 2010-08-10 12:44 UTC (permalink / raw)
  To: Tetsuo Handa; +Cc: kawime, linux-kernel

On Sat, 7 Aug 2010, Tetsuo Handa wrote:

> > Hi, i just compiled the 2.6.35-git3 kernel on my computer using debian 64 bit
> > as i did with all other kernels before.
> > Booting the git2/3 kernel results in a kernel panic because of
> > /sbin/tomoyo-init.
> > 
> > No problem with the 2.6.35 kernel.
> > 
> > I've to remane /sbin/tomoyo-init to boot the kernel.
> > Now i purged tomoyo-tools version 2.2.0-20100225 (aptitude purge tomoyo-tool) and everything works ok.
> > Sorry, i forgot to backup the tomoyo-init script.
> > 
> > $ uname -a
> > Linux xxxxxx 2.6.35-git3 #4 SMP Fri Aug 6 15:22:08 CEST 2010 x86_64 GNU/Linux
> 
> Thank you for using TOMOYO. TOMOYO has changed a lot in 2.6.36. Therefore,
> you need to upgrade tomoyo-tools package. I'm testing it now.
> You can upgrade it by doing
> 
> # wget -O tomoyo-tools.tar.gz 'http://sourceforge.jp/projects/tomoyo/svn/view/trunk/2.3.x/tomoyo-tools.tar.gz?root=tomoyo&view=tar'
> # tar -zxf tomoyo-tools.tar.gz
> # make -C tomoyo-tools/ install
> 
> Then, please delete (or rename) /etc/tomoyo/ directory and run
> /usr/lib/tomoyo/init_policy .
> 
> Please see http://tomoyo.sourceforge.jp/2.3/ for more information.

Still, if a legacy userspace application is able to cause kernel panic, 
that sounds like something we'd rather fix immediately.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
  2010-08-10 12:44   ` Jiri Kosina
@ 2010-08-10 20:14     ` Tetsuo Handa
  2010-08-10 20:35       ` Karsten Mehrhoff
  0 siblings, 1 reply; 6+ messages in thread
From: Tetsuo Handa @ 2010-08-10 20:14 UTC (permalink / raw)
  To: jkosina; +Cc: kawime, linux-kernel

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
  2010-08-10 20:14     ` Tetsuo Handa
@ 2010-08-10 20:35       ` Karsten Mehrhoff
  2010-08-11  9:18         ` Jiri Kosina
  0 siblings, 1 reply; 6+ messages in thread
From: Karsten Mehrhoff @ 2010-08-10 20:35 UTC (permalink / raw)
  To: jkosina, Tetsuo Handa; +Cc: linux-kernel

[Am 10.08.2010, 22:14 Uhr, schrieb Tetsuo Handa  
<penguin-kernel@i-love.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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3
  2010-08-10 20:35       ` Karsten Mehrhoff
@ 2010-08-11  9:18         ` Jiri Kosina
  0 siblings, 0 replies; 6+ messages in thread
From: Jiri Kosina @ 2010-08-11  9:18 UTC (permalink / raw)
  To: Karsten Mehrhoff; +Cc: Tetsuo Handa, linux-kernel

On Tue, 10 Aug 2010, Karsten Mehrhoff 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.

Looking at the code ...

	void tomoyo_check_profile(void)
	{
	        struct tomoyo_domain_info *domain;
	        const int idx = tomoyo_read_lock();
	        tomoyo_policy_loaded = true;
	        /* Check all profiles currently assigned to domains are defined. */
	        list_for_each_entry_rcu(domain, &tomoyo_domain_list, list) {
	                const u8 profile = domain->profile;
	                if (tomoyo_profile_ptr[profile])
	                        continue;
	                panic("Profile %u (used by '%s') not defined.\n",
	                      profile, domain->domainname->name);
	        }
	        tomoyo_read_unlock(idx);
	        if (tomoyo_profile_version != 20090903)
	                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");
	}

makes one wonder whether not having up-to-date userspace really does 
qualify for unconditional kernel panic.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-08-11  9:18 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-06 16:23 tomoyo-init (tomoyo-tools) results in kernel panic on kernel 2.6.35-git2/3 Karsten Mehrhoff
2010-08-07  5:04 ` Tetsuo Handa
2010-08-10 12:44   ` Jiri Kosina
2010-08-10 20:14     ` Tetsuo Handa
2010-08-10 20:35       ` Karsten Mehrhoff
2010-08-11  9:18         ` Jiri Kosina

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.