linux-kernel - Re: More issues found on kernel.org

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: <4CBCE039.2030501@kernel.org>
Date:	Mon, 18 Oct 2010 17:03:05 -0700
From:	"J.H." <warthog9@...nel.org>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: More issues found on kernel.org

On 10/18/2010 03:15 PM, Joel Becker wrote:
> On Mon, Oct 18, 2010 at 12:15:19PM -0700, J.H. wrote:
>> Not that the current discussion on IMA, and the recent problems found
>> with XFS were enough, I've started seeing, rather regularly, what I've
>> reported in bugzilla
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=20702
>>
>> It looks like a double free is happening somewhere, and the issue
>> *SEEMS* to be limited to the dynamic web boxes (bugzilla, wiki's, etc)
>> and those are the only boxes I have running drbd and ocfs2.
> 
> 	Obviously with no ocfs2 in the stack traces, it's hard to say
> anything from that perspective.  Do you have any idea what file snmpd is
> closing?

Wasn't pointing the finger at ocfs2, or drbd for that matter, was noting
that was running on the box as those are the only two boxes with it, and
those are the boxes having issues right now.  I'm at the point where I
have no idea *WHAT* was causing the problem just trying to get as much
info out there for debugging as possible.

As to what files snmpd was closing, no idea.  I'm using snmpd both for
monitoring of the boxes, but HP's utilities are using it for a pile of
things as well, including disk monitoring and such.  Could have been
just about anything unfortunately and I'm not sure there's a good way to
trap that if/when it happens again.

If I get to that state again is there anything that would be useful
(from a debugging perspective) to snag before the box falls over, I
might be able to get some sysrq requests back if anyone would find that
helpful, and might be able to poke around a bit, not sure how far I can
get before it becomes unusable yet.

- John 'Warthog9' Hawley
--
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/