From owner-freebsd-current@FreeBSD.ORG  Tue Oct  7 23:29:21 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mandree.no-ip.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 96F26E79;
 Tue,  7 Oct 2014 23:29:21 +0000 (UTC)
Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1])
 by apollo.emma.line.org (Postfix) with ESMTP id D6CE023CEED;
 Wed,  8 Oct 2014 01:29:19 +0200 (CEST)
Message-ID: <5434774F.5020708@FreeBSD.org>
Date: Wed, 08 Oct 2014 01:29:19 +0200
From: Matthias Andree <mandree@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Matthias Andree <mandree@FreeBSD.org>, 
 Antoine Brodin <antoine@freebsd.org>
Subject: Re: 11-CURRENT redports builders miscompiling?
References: <201410071915.s97JFrQo061043@svn.freebsd.org>
 <54343E60.7050208@FreeBSD.org>
 <CAALwa8k1EejjEk_HFFXVvLGyg4d69UWZoBhHkvydMf5yLe-FCA@mail.gmail.com>
 <543443CE.6000900@FreeBSD.org>
 <CAALwa8nc=wCBKCkcUQu9LOfBqr5NH8XqKxpTXhUDwGZBeQgEUA@mail.gmail.com>
 <543461CF.9040701@FreeBSD.org>
In-Reply-To: <543461CF.9040701@FreeBSD.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: freebsd-toolchain@freebsd.org,
 =?windows-1252?Q?Bernhard_Fr=F6hlich?= <decke@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Oct 2014 23:29:21 -0000

Am 07.10.2014 um 23:57 schrieb Matthias Andree:
> Am 07.10.2014 um 22:17 schrieb Antoine Brodin:
> 
>> So,  the test fail on head,  but if you look carefully,  1480342*1024
>> = 0x5a5a... which looks like malloc junk.
> 
> Bingo, thanks for the pointer.
> 
>> But when I turn off malloc debugging ( ln -s 'abort:false,junk:false'
>> /etc/malloc.conf ) the tests succeed.
>>
>> So it looks like a bug in e2fsprogs.
> 
> Yup, reproduced with "make post-build MALLOC_OPTIONS=J", and valgrind
> also has something to complain about, so I'll forward a report upstream.
> 
> I haven't seen something in the "maint" branch since the release that
> looks like an obvious fix.
> 
> This lets 11-CURRENT and redports off the hook for now.  I wasn't aware
> redports-on-11 set MALLOC_OPTIONS=J or equivalent.

I have bisected this on upstream's Git, and the failure-inducing change
is apparently 47fee2ef

<http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?h=maint&id=47fee2ef6a23ae06f680336ffde57caa64604a4c>

I reported this in greater detail to the authors/reviewers of the patch.

Let's see what we get.  For -current/-toolchain and decke@ I consider
this closed.

Thanks to Antoine for setting me on the right track.

Cheers,
Matthias