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: <alpine.DEB.2.10.1405071713590.7020@vincent-weaver-1.umelst.maine.edu>
Date:	Wed, 7 May 2014 17:17:22 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Cyrill Gorcunov <gorcunov@...il.com>
cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: perf_fuzzer crash on pentium 4

On Wed, 7 May 2014, Cyrill Gorcunov wrote:

> > I thought I was running with PeterZ's latest patch that was supposed to 
> > avoid the corruption.  Hmmm.  Let me reboot and try a few more things.
> 
> Thanks! Please ping me if find something new.

It turns out to be my fault, I was running with an incomplete version of 
PeterZ's patch.  We need to get the fix into the kernel as apparently I 
fail at manually applying patches across multiple machines.

So to summarize, with PeterZ's fix the various memory corruption crashes 
in the p4 code no longer happen.

When fuzzing on the p4 *other* things do happen.
	* at least two warnings pop up almost instantly
	* eventually the machine will crash in an endless NMI storm
	* also I managed to get the machine wedged with an unkillable
	  process, sort of like the known problem PeterZ has.

The NMI issue is probably the only one that is p4 related, and I do get 
the NMI warnings on other machines too, it's just the p4 is the only one 
where it brings down the machine.

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