linux-kernel - Re: 2.6.38-rc3 regression on parisc: segfaults

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: <20110203022420.A73F54E7B@hiauly1.hia.nrc.ca>
Date:	Wed, 2 Feb 2011 21:24:20 -0500 (EST)
From:	"John David Anglin" <dave@...uly1.hia.nrc.ca>
To:	mroos@...ux.ee (Meelis Roos)
Cc:	linux-parisc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.38-rc3 regression on parisc: segfaults

> I have been testing devel kernels on SMP L1000 successfully until 
> 2.6.38-rc2-00324-g70d1f36 included. The testing means booting the new 
> kernel and running aptitude to update to current debian unstable.
> 
> Now I tried 2.6.38-rc3 and got a crash from aptitude on 2 out of 2 
> tries. Maybe aptitude was broken inbetween but it looks like a kernel 
> bug. Retried 2.6.38-rc2-00324-g70d1f36 and that seemed to work fine so 
> it's more likely a kernel problem.

If aptitude fails consistently, it should be possible to debug or
isolate to a particular kernel change.  Usually, SMP segvs don't
provide much information as to the cause of the problem.  strace
output and a gdb backtrace would be useful.

I have seen improved SMP stability building with GCC 4.5.3 (try a
recent snap).  This fixes an asm/branch problem.  It seems like James'
flush patch hasn't been pulled.

Dave
-- 
J. David Anglin                                  dave.anglin@...-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
--
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/