Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752510AbbBXHk6 (ORCPT ); Tue, 24 Feb 2015 02:40:58 -0500 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:57936 "EHLO e06smtp10.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751436AbbBXHk4 (ORCPT ); Tue, 24 Feb 2015 02:40:56 -0500 Message-ID: <54EC2B04.9070406@de.ibm.com> Date: Tue, 24 Feb 2015 08:40:52 +0100 From: Christian Borntraeger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mike Galbraith CC: Linus Torvalds , Linux Kernel Mailing List , jseward@acm.org Subject: Re: Linux 4.0-rc1 out.. References: <54EB4A98.6020300@de.ibm.com> <1424745296.10678.12.camel@gmail.com> In-Reply-To: <1424745296.10678.12.camel@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15022407-0041-0000-0000-00000358901A Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2368 Lines: 56 Am 24.02.2015 um 03:34 schrieb Mike Galbraith: > On Mon, 2015-02-23 at 16:43 +0100, Christian Borntraeger wrote: >> Am 23.02.2015 um 04:06 schrieb Linus Torvalds: >>> .. let's see how much, if anything, breaks due to the version number. >>> Probably less than during the 3.0 timeframe, but I can just imagine >>> somebody checking for meaningful versions. >>> >>> Because the people have spoken, and while most of it was complete >>> gibberish, numbers don't lie. People preferred 4.0, and 4.0 it shall >>> be. Unless somebody can come up with a good argument against it. >> >> The only argument that I can come up with is "we do not break userspace". >> For example there is this "gem" in configure.ac of valgrind: >> >> >> case "${kernel}" in >> 2.6.*|3.*) >> AC_MSG_RESULT([2.6.x/3.x family (${kernel})]) >> AC_DEFINE([KERNEL_2_6], 1, [Define to 1 if you're using Linux 2.6.x or Linux 3.x]) >> ;; >> >> 2.4.*) >> AC_MSG_RESULT([2.4 family (${kernel})]) >> AC_DEFINE([KERNEL_2_4], 1, [Define to 1 if you're using Linux 2.4.x]) >> ;; >> >> *) >> AC_MSG_RESULT([unsupported (${kernel})]) >> AC_MSG_ERROR([Valgrind works on kernels 2.4, 2.6]) >> ;; > > > Heh, if this is an argument, we have one hell of a lot of reverting to > do :) Crash for example breaks at much higher resolution, and indeed > just broke yet again. Tough titty for userspace methinks. Well crash is not a good example as it by design goes beyond the user ABI and directly touches the kernel data structures ;-) I am not requesting to go back to 3.*, I was just pointing out that if we apply strict rules on "we dont break userspace", the move to 3.* and 4.* was a mistake. We do provide uname26 as a workaround, so this is ok and the switch to 4 should be a lot smoother. But better end the discussion here :-) Christian FWIW, valgrind svn is fixed as of yesterday (for good, so Linux 5.* 6.*.. should also work) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/