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: <8E8F647D7835334B985D069AE964A4F7028FE67D@ECQCMTLMAIL1.quebec.int.ec.gc.ca>
Date:	Fri, 23 Mar 2007 11:53:07 -0400
From:	"Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>
To:	"Andy Whitcroft" <apw@...dowen.org>,
	"Con Kolivas" <kernel@...ivas.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>, "Steve Fox" <drfickle@...ibm.com>,
	"Martin J. Bligh" <mbligh@...igh.org>
Subject: RE: 2.6.21-rc4-mm1

> 
> Andy Whitcroft wrote:
> > Con Kolivas wrote:
> >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> >>> Ok, I have yet a third x86_64 machine is is blowing up with the 
> >>> latest
> >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with 
> >>> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix 
> >>> levels so I have just fired off a set of tests across the affected

> >>> machines on that latest hotfix stack plus the RSDL backout and the

> >>> results should be in in the next hour or two.
> >>>
> >>> I think there is a strong correlation between RSDL and these
hangs.  
> >>> Any suggestions as to the next step.
> >> Found a nasty in requeue_task
> >> +	if (list_empty(old_array->queue + old_prio))
> >> +		__clear_bit(old_prio, p->array->prio_bitmap);
> >>
> >> see anything wrong there? I do :P
> >>
> >> I'll queue that up with the other changes pending and hopefully
that 
> >> will fix your bug.
> > 
> > Tests queued with your rdsl-0.33 patch (I am assuming its in there).
> > Will let you know how it looks.
> 
> Hmmm, this is good for the original machine (as was 0.32) but 
> not for either of the other two.  I am seeing panics as below 
> on those two.
> 
> -apw
> 

I don't know if this might help out or even if it is related but I get a
"similar" crash every time using my backported rsdl patch on a 2.6.19.7
kernel.  "Maybie" this type of BUG might be easier to trigger under that
specific kernel?  Here is a picture of the output:
http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/bug-2.6.19
.7-rsdl-033.jpg.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ