From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8B7121381FA for ; Tue, 13 May 2014 19:39:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AE590E09E4; Tue, 13 May 2014 19:39:16 +0000 (UTC) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by pigeon.gentoo.org (Postfix) with ESMTP id C764CE09DD for ; Tue, 13 May 2014 19:39:15 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta01.emeryville.ca.mail.comcast.net with comcast id 1TCi1o00G1afHeLA1XfFD6; Tue, 13 May 2014 19:39:15 +0000 Received: from [192.168.1.13] ([50.190.84.14]) by omta17.emeryville.ca.mail.comcast.net with comcast id 1XfD1o00D0JZ7Re8dXfEGf; Tue, 13 May 2014 19:39:15 +0000 Message-ID: <537274D8.4040408@gentoo.org> Date: Tue, 13 May 2014 15:39:04 -0400 From: Joshua Kinard User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-hardened@lists.gentoo.org Reply-to: gentoo-hardened@lists.gentoo.org MIME-Version: 1.0 To: gentoo-hardened@lists.gentoo.org Subject: Re: [gentoo-hardened] Weird coincidental PAX crashes References: <536CF0F7.3030602@gentoo.org> <536CF473.9050103@gomersbach.nl> <536CF69E.5080009@gentoo.org> <98626617c230cc350af99343bde03183.squirrel@atoth.sote.hu> <536E0A15.7070603@gentoo.org> <536E0FD5.2050509@gentoo.org> <536E2D16.7060503@opensource.dyc.edu> In-Reply-To: <536E2D16.7060503@opensource.dyc.edu> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1400009955; bh=6Ta+Z3JUkuIah6ZHwvsH+nfWLuInrEAbBCu1ljzV1CE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=k3dsPf3K6zVE3foAczQ7FJg5rj8Q7CyNDltIM10JLnIIucjcAYW8aVSzo/Xyh1e4S RIrqDkEEovI9zPLfeyy6Z/2E5bevYcI+PDMZKvKY3Jcb0x9q/G2uZbskPc1uCsxJkV Qt56r5aiS6VVZXNKjUAGngTMKQ5zLIZra+pgClwsapF/XwSQ4piiiP1O0DCxkJud5f j6cf7KwXRPxVV0lhDqvlb1xKqntZl/yQ6Ee9jr4WchA9dGBVt0MBKmOsOB4EqiutAJ J2YZe4VpSf45zuzJSUcpLJV+4RDxZzSQHdINyOBhQo9qI69UlkLL/wUyd/nbVlWUD6 WLey/NgQcvYSg== X-Archives-Salt: 50d36658-c5f0-4b7b-8dd2-2c55529a00a6 X-Archives-Hash: 6dba481f19cecd140f901dfcab3d1908 On 05/10/2014 09:43, Anthony G. Basile wrote: > On 05/10/14 07:39, Michael Orlitzky wrote: >> On 05/10/2014 07:14 AM, Joshua Kinard wrote: >>> >>> I think I ran into this, too, in 3.11. It takes a few days of uptime before >>> it happens. Running 3.13.x now on my x64 machine and haven't ran into it >>> again. So I second the suggestion to upgrade your kernel. >>> >> >> I couldn't come up with a better idea, so last night I upgraded >> everything to hardened-sources-3.13.6-r3. >> > > Unfortunately I don't know what the "this" is because that trace stripped > all symbols --- at least in kernel land. In useland its pretty obvious: > refcount overflow detected in: syslog-ng. So some syscall initiated by > syslog-ng is hitting up against the overflow. An strace might tell us what > syscall, but it might be hard to go from there to where in the kernel the > overflow happens. > > Not to sound like a snotty dev, but please open bugs with these oopses so we > have a record in bugzilla. Email just buries this info. For me, I never had an actual oops. Just a note in dmesg that pax was killing command-line processes at random. Running services didn't seem to be affected, but I could go run grep or something and it'd just abruptly terminate. Kinda hard to file a bug on that and not have it closed as WONTFIX :) -- Joshua Kinard Gentoo/MIPS kumba@gentoo.org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic