linux-kernel - Re: shm updates broke UML

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:	Mon, 1 Aug 2011 21:24:52 +0400
From:	Vasiliy Kulikov <segoon@...nwall.com>
To:	Marc Zyngier <marc.zyngier@....com>
Cc:	Richard Weinberger <richard@....at>, serge.hallyn@...onical.com,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net, toralf.foerster@....de
Subject: Re: shm updates broke UML

On Mon, Aug 01, 2011 at 19:19 +0200, Marc Zyngier wrote:
> Here you go (sorry about the line wrapping, damned webmail...):

Thank you!  Now I see that the problem is rw_mutex is not initialized:

	down_write(&shm_ids(ns).rw_mutex);

void __sched __down_write_nested(struct rw_semaphore *sem, int subclass)
{
    ...
	if (sem->activity == 0 && list_empty(&sem->wait_list)) {
                                         ^^^^^^^^^^^^^^^ is NULL

Wtf - ipc namespace should be fully initialized for the moment of
threads run...

> Calibrating local timer... 104.99MHz.
> CPU1: Booted secondary processor
> CPU1: Unknown IPI message 0x1
> CPU2: Booted secondary processor
> CPU2: Unknown IPI message 0x1
> CPU3: Booted secondary processor
> CPU3: Unknown IPI message 0x1
> Brought up 4 CPUs
> SMP: Total of 4 processors activated (333.41 BogoMIPS).
> ns = c0447474, ids = c04474d0
> ns = c0447474, ids = c04474d0
> wait_list = c04474e0
> next =   (null)
           ^^^^^^

-- 
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
--
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/