Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3975284pxb; Mon, 8 Feb 2021 05:08:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJwrOtv3xFSzGlo+3BVgoQz5THZxAtb7PDb2Yam7gVb/UN/fv67WRvSlvxIlg6Dz1yL3NN1X X-Received: by 2002:a17:906:4e84:: with SMTP id v4mr2511598eju.44.1612789682662; Mon, 08 Feb 2021 05:08:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612789682; cv=none; d=google.com; s=arc-20160816; b=G6TCpbeXYQM9gHU6Frlo4nTzcGqSyVa/4bFedIL8cwe3UjCiok7QH5b8YBJ04JPM5r WUpx9Mj2lcLQL2WXFv9lLG4MItIi84/bjfU2p0EpxGuvj5PeE+T5eIPBtmfgbHLqDAEb I6ZV9XKmJwHakyNal6EARI46pil8iPg//kpLgulcXQ/XzaMxjuqIfFJT81OFPEEWyYxW CUxu5z9QD8oTDRF3Ohf0pm2WGWaZYahqm3KJ62fGSfsRWm+eRmwNHazCLXA1k//f78tB xbX8eXhg1OGrfBwdMo8v1q0DeAcRqScrDhlXbRJOfSCy2L6u3r+gksJhGg5KAJ2CQx9c nzFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=6ovK+r6VZYcL2sV7f+ru0WoK+un+a755XwVvRqNcYBk=; b=lQqgmlM1mZizbsPAjhCcUo8DRgBxAQq2d9lofDZRJniAazGpvY8Kvtn2Jbemmt2WSI DncljF6r2ejqLaIu37PlLtEg+TDdI/o2Bf7wSPWz1IFFcqWQ59Aj1+0jCa97tHnWk3yg FRNApL2omOZlVKvNeVkO4ZjzTMAq9TnNTwiy3CzwkpEOtINobMIVLhIYOF6lo/o9ycZs G+xzBEbVwzFAVWJWkc2YkH/EYGU1Q9qIzWUyPci0Gxdx7Gqw7/c14YqZpq5ghQSz4BJk zRCEwUjbDySZ65pyKaPHjUYWa9Op6clO/tC+FBIZyNreHj9ke0Uf9+PVWKgKiZbopJxy Li8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ghDqYqgI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j4si1071590ejm.600.2021.02.08.05.07.37; Mon, 08 Feb 2021 05:08:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ghDqYqgI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230166AbhBHNEY (ORCPT + 99 others); Mon, 8 Feb 2021 08:04:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:53678 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229993AbhBHNEO (ORCPT ); Mon, 8 Feb 2021 08:04:14 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7E25664DEE; Mon, 8 Feb 2021 13:03:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1612789410; bh=bETiuTGyJzRrkPM08sFMEeeymGXeVkr5IZqwRHPvyuk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ghDqYqgIHwdgMylS8xDfalMdh0lwSDhYYj9PatglZwRF/yuzcobiCOvBvBKYi6Naz ntHzmE9EewGbXLu3tb2Nyqd2eHOIkck24IhG3wl3tjW+mpfa4eeLVdYR2P8g8VKQG5 YmHWJtO0MNPYVCsJDM+bB2ti77mWzrsWj2wplxzc= Date: Mon, 8 Feb 2021 14:03:27 +0100 From: Greg Kroah-Hartman To: Florian Weimer Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net, jslaby@suse.cz Subject: Re: Linux 4.9.256 Message-ID: References: <1612535085125226@kroah.com> <87czxa3efr.fsf@oldenburg.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87czxa3efr.fsf@oldenburg.str.redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 08, 2021 at 01:57:12PM +0100, Florian Weimer wrote: > * Greg Kroah-Hartman: > > > I'm announcing the release of the 4.9.256 kernel. > > > > This, and the 4.4.256 release are a little bit "different" than normal. > > > > This contains only 1 patch, just the version bump from .255 to .256 which ends > > up causing the userspace-visable LINUX_VERSION_CODE to behave a bit differently > > than normal due to the "overflow". > > > > With this release, KERNEL_VERSION(4, 9, 256) is the same as KERNEL_VERSION(4, 10, 0). > > > > Nothing in the kernel build itself breaks with this change, but given > > that this is a userspace visible change, and some crazy tools (like > > glibc and gcc) have logic that checks the kernel version for different > > reasons, I wanted to do this release as an "empty" release to ensure > > that everything still works properly. > > I'm looking at this from a glibc perspective. glibc took the > KERNEL_VERSION definition and embedded the bit layout into the > /etc/ld.so.cache, as part of the file format. Exact impact is still > unclear at this point. If we "cap" this at 4, 9, 255 according to what userspace sees, will that be a problem if we increase the number reported by uname(2)? And when is the ld.so.cache file "regenerated"? thanks, greg k-h