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: <20091012135628.GA310@grsecurity.net>
Date:	Mon, 12 Oct 2009 09:56:28 -0400
From:	spender@...ecurity.net (Brad Spengler)
To:	Matthew Wilcox <matthew@....cx>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] pci: fix crash about old IA64 about pci_cfg_space_size

> So how about we go back to adding that check ... this does require that
> SGI's 750 machine reports its SAL revision correctly.  Could you send
> the dmesg?

The dmesg of the working kernel:
http://grsecurity.net/~spender/dmesg.txt
The output of lspci -vvxxxx:
http://grsecurity.net/~spender/lspci1.txt
The output of lspci -tvnn:
http://grsecurity.net/~spender/lspci2.txt

I don't have a serial console hooked up to the machine, and I'm not able 
to scroll up/down after the panic, so I only have the following picture 
from the crash.  I modified the code that spews out registers on a panic 
so that the context of the panic could be seen.  The stack trace didn't 
show anything useful, only repeats of an address similar to IP (for 
which no symbols exist).
http://img132.yfrog.com/i/img1457u.jpg/

-Brad

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ