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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140502162234.GX11096@twins.programming.kicks-ass.net>
Date:	Fri, 2 May 2014 18:22:34 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [perf] more perf_fuzzer memory corruption

On Fri, May 02, 2014 at 12:22:30PM -0400, Vince Weaver wrote:
> 
> I'll try the patch next.
> 
> Meanwhile, can polling on a closed event cause problems with the reference 
> count?
> 
> In my various failure traces there's always been a poll() active at the 
> time of crash, and I added some trace_printk()s and it looks like poll is 
> at least attempting to poll on the closed file descriptor that's causing 
> us problems.

In principle the vfs file refcounting should be responsible for that.
But I'll go over it in a bit.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ