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 12:22:36 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Nicolas Pitre <nicolas.pitre@...aro.org>
Cc:	Pavel Machek <pavel@....cz>, Marc Zyngier <marc.zyngier@....com>,
	Russell King <rmk+kernel@....linux.org.uk>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert 9fc2105aeaaf56b0cf75296a84702d0f9e64437b to fix
 pyaudio (and probably more)

On Sun, Jan 4, 2015 at 12:03 PM, Nicolas Pitre <nicolas.pitre@...aro.org> wrote:
>
> NAK.

To quote the standard response for people who ignore regressions:

  "SHUT THE FUCK UP"

you cannot NAK regression fixes. Seriously.

I don't understand how people can't get this simple thing.

You have two choices:

 - acknowledge and fix regressions

 - get the hell out of kernel development.

It really is that simple. I really don't get why people don't
understand this simple first rule of kernel development. Is it really
not widely enough documented?

No regressions. If user mode breaks, it is absolutely *never*
acceptable to blame user mode.

Occasionally there may be major overriding reasons (security issue,
whatever), but even then we bend over *backwards* trying to make sure
breakage is minimal.

Christ people. Why does this even have to be discussed any more?

And I realize that ARM people may not be used to this whole "user mode
matters" thing, what with all the crazy hardware incompatibilities.
But you guys need to shape up. We don't break things. Not even on ARM.

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