NetBSD Problem Report #54062

From gson@gson.org  Sat Mar 16 11:54:05 2019
Return-Path: <gson@gson.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 4E6F97A188
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 16 Mar 2019 11:54:05 +0000 (UTC)
Message-Id: <20190316115359.7D7D89894DA@guava.gson.org>
Date: Sat, 16 Mar 2019 13:53:59 +0200 (EET)
From: gson@gson.org (Andreas Gustafsson)
Reply-To: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@NetBSD.org
Subject: lib/libc/sys/t_sendmmsg/sendmmsg_basic test regression
X-Send-Pr-Version: 3.95

>Number:         54062
>Category:       kern
>Synopsis:       lib/libc/sys/t_sendmmsg/sendmmsg_basic test regression
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    christos
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 16 11:55:00 +0000 2019
>Closed-Date:    Sun Mar 17 11:23:49 +0000 2019
>Last-Modified:  Sun Mar 17 11:23:49 +0000 2019
>Originator:     Andreas Gustafsson
>Release:        NetBSD-current
>Organization:

>Environment:
System: NetBSD
Architecture: x86_64
Machine: amd64
>Description:

The lib/libc/sys/t_sendmmsg/sendmmsg_basic test case has recently
started failing in every run.

It was previously passing reliably on my testbed on real amd64
hardware, and passing most of the time on the qemu-based TNF i386
testbed.

The problem started during the recent period when the tests were
panicing the system due to pmap bugs, which makes it harder to pin
down the offending commit.  The first failure recorded on b5 is here:

  http://releng.netbsd.org/b5reports/i386/commits-2019.03.html#2019.03.12.11.05.09

>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:
From: Andreas Gustafsson <gson@gson.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/54062: lib/libc/sys/t_sendmmsg/sendmmsg_basic test regression
Date: Sat, 16 Mar 2019 17:17:59 +0200

 Earlier today, I wrote:
 > The problem started during the recent period when the tests were
 > panicing the system due to pmap bugs, which makes it harder to pin
 > down the offending commit.

 I was wrong - the problem actually started one commit before said period,
 with this commit:

   2019.03.10.15.32.42 christos src/external/bsd/jemalloc/lib/Makefile.inc 1.5

 The lib/libc/stdio/t_printf:snprintf_float test also started failing
 at the same time.

 Logs at:

   http://www.gson.org/netbsd/bugs/build/amd64-baremetal/commits-2019.03.html#2019.03.10.15.32.42

 -- 
 Andreas Gustafsson, gson@gson.org

Responsible-Changed-From-To: kern-bug-people->christos
Responsible-Changed-By: gson@NetBSD.org
Responsible-Changed-When: Sat, 16 Mar 2019 15:22:33 +0000
Responsible-Changed-Why:
Over to committer.


From: "Christos Zoulas" <christos@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/54062 CVS commit: src/external/bsd/jemalloc/dist/src
Date: Sat, 16 Mar 2019 17:32:05 -0400

 Module Name:	src
 Committed By:	christos
 Date:		Sat Mar 16 21:32:04 UTC 2019

 Modified Files:
 	src/external/bsd/jemalloc/dist/src: extent.c

 Log Message:
 PR/54062: Fix the "snprintf_float" test failing after the jemalloc import
 issue: jemalloc uses a lot more memory (if it can find it) by default and
 this test limited the amount of memory it could get, causing it to get to
 an error path with a missing mutex_unlock...


 To generate a diff of this commit:
 cvs rdiff -u -r1.3 -r1.4 src/external/bsd/jemalloc/dist/src/extent.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

From: "Christos Zoulas" <christos@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/54062 CVS commit: src/tests/lib/libc/sys
Date: Sat, 16 Mar 2019 17:46:43 -0400

 Module Name:	src
 Committed By:	christos
 Date:		Sat Mar 16 21:46:43 UTC 2019

 Modified Files:
 	src/tests/lib/libc/sys: t_sendmmsg.c

 Log Message:
 PR/54062: Using random garbage in the mmsghdr (in this case 0xa5's from
 jemalloc debug) makes the syscall unhappy. Zero out the memory instead...


 To generate a diff of this commit:
 cvs rdiff -u -r1.2 -r1.3 src/tests/lib/libc/sys/t_sendmmsg.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed
State-Changed-By: gson@NetBSD.org
State-Changed-When: Sun, 17 Mar 2019 11:23:49 +0000
State-Changed-Why:
Fixed by christos - thanks!


>Unformatted:

Home	PR Database Search