linux-kernel - Re: [Bug] 2.6.18-rc4-mm2 panic in __unix_insert_socket x86

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] [day] [month] [year] [list]

Message-ID: <20060825152428.GB8909@in.ibm.com>
Date:	Fri, 25 Aug 2006 11:24:28 -0400
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	Andi Kleen <ak@...e.de>
Cc:	kmannth@...ibm.com, lkml <linux-kernel@...r.kernel.org>,
	andrew <akpm@...l.org>
Subject: Re: [Bug] 2.6.18-rc4-mm2 panic in __unix_insert_socket x86_64

On Fri, Aug 25, 2006 at 08:29:46AM +0200, Andi Kleen wrote:
> On Friday 25 August 2006 04:20, keith mannthey wrote:
> > On Tue, 2006-08-22 at 17:39 -0700, keith mannthey wrote:
> > > Hello all,
> > >   Something from mm1 to mm2 brought this bug out. I didn't see any
> > > change in the unix socket code so I am not sure where to start. I am
> > > going to start bisecting patches. 2.6.18-rc4-mm1 was working as
> > > expected.  I have already stepped around afs and smp alternatives errors
> > > but I haven't seen any errors related to this posted yet.
> > 
> > 
> > Ok finally finished all the rebuilds/reboots needed find the trouble
> > patch.  What seems to be causing the problem is listed as 
> > 
> > Re-positioning the bss segment   or 
> > x86_64-mm-re-positioning-the-bss-segment.patch
> > 
> > It seems something is getting trampled.  Thoughts?
> 
> Hmm, it seems to be outside _edata now. There are a couple of references,
> but I'm not sure they actually matter
> 

It was outside _edata even before. So that should not make any difference.
It boots fine on my machine. Strange. I am looking into it.

Thanks
Vivek

-
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/