From: Avi Kivity <avi@scylladb.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 4.9.256
Date: Mon, 8 Feb 2021 17:50:21 +0200 [thread overview]
Message-ID: <23a28990-c465-f813-52a4-f7f3db007f9d@scylladb.com> (raw)
In-Reply-To: <1612535085125226@kroah.com>
On 05/02/2021 16.26, Greg Kroah-Hartman wrote:
> 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).
I think this is a bad idea. Many kernel features can only be discovered
by checking the kernel version. If a feature was introduced in 4.10,
then an application can be tricked into thinking a 4.9 kernel has it.
IMO, better to stop LINUX_VERSION_CODE at 255 and introduce a
LINUX_VERSION_CODE_IMPROVED that has more bits for patchlevel.
> 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.
Even if glibc and gcc work, other programs may not.
I have two such cases. They don't depend on 4.9, but they're examples of
features that are not discoverable by other means.
> So, this is a YOU MUST UPGRADE requirement of a release. If you rely on the
> 4.9.y kernel, please throw this release into your test builds and rebuild the
> world and let us know if anything breaks, or if all is well.
>
> Go forth and do full system rebuilds! Yocto and Gentoo are great for this, as
> will systems that use buildroot.
>
> I'll try to hold off on doing a "real" 4.9.y release for a 9eek to give
> everyone a chance to test this out and get back to me. The pending patches in
> the 4.9.y queue are pretty serious, so I am loath to wait longer than that,
> consider yourself warned...
>
> The updated 4.9.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
> thanks,
>
> greg k-h
>
> ------------
>
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Greg Kroah-Hartman (1):
> Linux 4.9.256
>
>
next prev parent reply other threads:[~2021-02-08 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 14:26 Linux 4.9.256 Greg Kroah-Hartman
2021-02-05 14:26 ` Greg Kroah-Hartman
2021-02-08 12:57 ` Florian Weimer
2021-02-08 13:03 ` Greg Kroah-Hartman
2021-02-08 15:50 ` Avi Kivity [this message]
2021-02-08 16:31 ` Greg Kroah-Hartman
2021-02-08 18:57 ` Sasha Levin
2021-02-09 8:53 ` Avi Kivity
2021-02-11 10:48 ` LINUX_VERSION_CODE overflow (was: Re: Linux 4.9.256) Florian Weimer
2021-02-11 12:58 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23a28990-c465-f813-52a4-f7f3db007f9d@scylladb.com \
--to=avi@scylladb.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).