From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-4722-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 10324 invoked by alias); 2 May 2006 16:18:55 -0000
Received: (qmail 10240 invoked by uid 48); 2 May 2006 16:18:19 -0000
Date: Tue, 02 May 2006 16:18:00 -0000
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20060502161811.2632.pasky@suse.cz>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug nscd/2632] New: db not properly initialized
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2006-05/txt/msg00018.txt.bz2
List-Id: <glibc-bugs.sourceware.org>

memset() clearing the dbs head structure had wrong size parameter. This was
causing certain values (like nentries) to be incremented from random starting
values, possibly leading to random crashes.

Reported and patch by Kevin Rudd.

-- 
           Summary: db not properly initialized
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nscd
        AssignedTo: drepper at redhat dot com
        ReportedBy: pasky at suse dot cz
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2632

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.