linux-kernel - Re: lguest: unhandled trap 13 in current -rc

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: <49B10641.9070908@trash.net>
Date:	Fri, 06 Mar 2009 12:17:21 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: lguest: unhandled trap 13 in current -rc

Rusty Russell wrote:
> On Thursday 05 March 2009 00:42:39 Patrick McHardy wrote:
>> Patrick McHardy wrote:
>>> When trying to run lguest in the current -rc, I get an "unhandled
>>> trap 13" and it stops. The address resolves to the rdmsr intruction
>>> in native_read_msr_safe(). -rc2 works fine, but I couldn't find
>>> any changes that looks related.
>>>
>>> .config is attached, more information available on request.
>> For the record, this is still broken in -rc7.
> 
> (Sorry, I missed the first mail to lkml).
> 
> Reproduced on one of my test machines (kvm doesn't show the problem here).
> 
> Subject: lguest: fix crash 'unhandled trap 13 at <native_read_msr_safe>'


Thanks Rusty, this fixed the problem for me.

There's a second problem, outgoing network performance using a routed
tap-interface is in the area of 20-30 kbit/second. I noticed this
previously (which is why I wanted to test the latest version), in
-rc2 what still worked was turning TSO/GSO etc. off, this seems to
be without effect in -rc7. I'll have a look at this myself tommorrow
unless someone beats me to it :)
--
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/