linux-kernel - Re: [ 00/78] 3.3.2-stable review

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:	Thu, 12 Apr 2012 18:12:56 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	felipe.contreras@...il.com
Cc:	torvalds@...ux-foundation.org, gregkh@...uxfoundation.org,
	lists@...e.net, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, linux-wireless@...r.kernel.org,
	c_manoha@....qualcomm.com, ath9k-devel@...ema.h4ckr.net,
	linville@...driver.com
Subject: Re: [ 00/78] 3.3.2-stable review

From: Felipe Contreras <felipe.contreras@...il.com>
Date: Fri, 13 Apr 2012 01:04:42 +0300

> Wrong is wrong, before or after the 3.3.1 tag, this patch is not
> 'stable' material, and removing it does not affect upstream at all.

What you don't understand is that bug fixes will get lost if you only
fix them in -stable, it doesn't matter HOW THEY GOT into -stable.

In fact IT HAS FUCKING HAPPENED that we didn't fix something upstream
that got fixed in -stable a time long ago when we didn't have the
policy we're using now which you're going so unreasonably ape-shit
about.

And we didn't notice the discrepency until much later.

So the issues are real, there's proven precendence, and you're just
so wrong it's not even funny.

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