linux-kernel - Re: [PATCH 3.12 000/104] 3.12.27-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]

Message-Id: <20140823.111035.1932350736810442438.davem@davemloft.net>
Date:	Sat, 23 Aug 2014 11:10:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linux@...ck-us.net
Cc:	jslaby@...e.cz, stable@...r.kernel.org, satoru.takeuchi@...il.com,
	shuah.kh@...sung.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3.12 000/104] 3.12.27-stable review

From: Guenter Roeck <linux@...ck-us.net>
Date: Sat, 23 Aug 2014 08:14:54 -0700

> On 08/21/2014 01:05 AM, Jiri Slaby wrote:
>> The last three are just cosmetical in 3.12. And I do not immediately
>> see
>> in the rest, how they could improve the state. So I am going to remove
>> the add-basic-validations patch from 3.12.
>>
> 
> Build and tests now look good.

I am hugely disappointed in this.

This is why I really do all the backports for each -stable release
myself and I therefore really wish there was more thought put into
when these changes are placed into other trees.

Almost all of those sparc64 memory management fixes should not go into
anything before v3.13, because all of these fixes are in the context
of the page tables encoding PMDs using the PTE layout.

If you're just forcing changes you see go into other -stable
submissions into your tree until they compile, and just hoping that a
tester will catch any problems, you are absolutely doing it wrong and
taking a large amount of value out of the -stable releases.

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