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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 10 Aug 2010 14:44:28 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:	kawime@....de, linux-kernel@...r.kernel.org
Subject: Re: tomoyo-init (tomoyo-tools) results in kernel panic on kernel
 2.6.35-git2/3

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.

--
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/