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.1501081044470.26196@pianoman.cluster.toy>
Date:	Thu, 8 Jan 2015 10:44:53 -0500 (EST)
From:	Vince Weaver <vince@...ter.net>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
cc:	Catalin Marinas <catalin.marinas@....com>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pavel Machek <pavel@....cz>,
	Marc Zyngier <marc.zyngier@....com>,
	kernel list <linux-kernel@...r.kernel.org>,
	vincent.weaver@...ne.edu
Subject: Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix
 pyaudio (and probably more)

On Thu, 8 Jan 2015, Russell King - ARM Linux wrote:

> It's not a regression - yet.  No one has shown that userspace has broken
> according to the definition of the first quote above, and that's the
> whole point.

How much does one have to regress before it is a problem?  I have two 
projects I've worked on that "broke" due to this issue.  

They were minor breakages though.

The "linux_logo" userspace sysinfo tool broke to the extent that it 
was parsing for the bogomips string in /proc/cpuinfo and printed poorly 
formatted and/or corrupted text info to screen when it couldn't find it.

The "PAPI" library had some really ancient (and poorly 
thought-out) fallback code that would try to estimate MHz from bogomips 
if a MHz value was not available via the traditional methods.  This
failed after the change too, but not many people use PAPI on ARM so it 
wasn't that big an issue.

I noticed these problems early, even before the change hit mainline.
But when I complained I was told in no uncertain terms that the ARM
maintainers were tired of hearing about bogomips issues and nothing
could be done to stop the change from getting in.

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