linux-kernel - Re: [PATCH] Fix initialization of runqueues

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]

Message-ID: <20060802165742.GI4460@implementation.labri.fr>
Date:	Wed, 2 Aug 2006 18:57:42 +0200
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix initialization of runqueues

Ingo Molnar, le Wed 02 Aug 2006 17:24:19 +0200, a écrit :
> 
> * Samuel Thibault <samuel.thibault@...-lyon.org> wrote:
> 
> > Hi,
> > 
> > There's an odd thing about the nr_active field in arrays of 
> > runqueue_t: it is actually never initialized to 0!...  This doesn't 
> > yet trigger a bug probably because the way runqueues are allocated 
> > make it so that it is already initialized to 0, but that's not a safe 
> > way.  Here is a patch:
> 
> we do rely on zero initialization of bss (and percpu) data in a number 
> of places.

The rest of runqueue initialization doesn't rely on that, and as
a result people might think that it is safe to allocate runqueues
dynamically.

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