linux-kernel - Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix pyaudio (and probably more)

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]

Date:	Sun, 4 Jan 2015 15:25:02 -0500 (EST)
From:	Nicolas Pitre <nicolas.pitre@...aro.org>
To:	Pavel Machek <pavel@....cz>
cc:	marc.zyngier@....com, rmk+kernel@....linux.org.uk,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix
 pyaudio (and probably more)

On Sun, 4 Jan 2015, Pavel Machek wrote:

> On Sun 2015-01-04 15:03:02, Nicolas Pitre wrote:
> > If that is still unacceptable to you for whatever reason, then the least 
> > wrong compromize should be:
> > 
> > 	seq_printf(m, "BogoMIPS\t: 1.00\n");
> > 
> > That'D allow for those broken applications to run while making clear 
> > that the provided value is phony. I was about to suggest 0.00 but that 
> > could trigger a divide by zero error somewhere I suppose.
> 
> I don't know what 1.00 will cause, and neither do you, so what about
> simply reverting the bad patch?

Because the patch wasn't "bad".  It did solve a recurring support 
problem where people did actually complain on the list because the value 
was not what they would have liked.  Removing this meaningless value did 
actually fix that support issue as no more complaints came through for 
the last 1.3 year, and is actually the only way for user space to be 
fixed too.


Nicolas
--
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/