From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Dominik Brodowski" <linux@dominikbrodowski.net>,
"Cyrill Gorcunov" <gorcunov@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
YueHaibing <yuehaibing@huawei.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Jann Horn" <jannh@google.com>,
"Kees Cook" <keescook@chromium.org>
Subject: Re: [PATCH] kernel/sys.c: Fix UNAME26 for 5.0
Date: Tue, 8 Jan 2019 01:08:54 +0100 [thread overview]
Message-ID: <20190108000854.GD3987@latitude> (raw)
In-Reply-To: <CAHk-=wgAH7QZrAyzaTV1-6MecaSdVkiowSZEM7qwa0L2oegpLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Mon, Jan 07, 2019 at 10:10:31AM -0800, Linus Torvalds wrote:
> On Mon, Jan 7, 2019 at 10:03 AM Jonathan Neuschäfer
> <j.neuschaefer@gmx.net> wrote:
> >
> > UNAME26 is a mechanism to report Linux's version as 2.6.x, for
> > compatibility with old/broken software. Because of the way it is
> > implemented, it needs to be adjusted to handle version 5.0.
>
> Do we actually need this?
I don't run any such old software, so I don't have a strong opinion
here; I just sent this patch because I knew UNAME26 version strings
would jump back without it.
> I'd rather let it bitrot, and just let it return random versions. It
> will just start again at 2.4.60, won't it?
Correct.
(Well, it's 2.6, not 2.4, but yes)
> Anybody who uses UNAME26 for a 5.x kernel might as well think it's
> still 4.x. The user space is so old that it can't possibly care about
> differences between 4.x and 5.x, can it?
>
> The only thing that matters is that it shows "2.4.<largeenough>",
> which it will do regardless.
Good point, I guess that's a valid appraoch.
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-08 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 18:03 [PATCH] kernel/sys.c: Fix UNAME26 for 5.0 Jonathan Neuschäfer
2019-01-07 18:10 ` Linus Torvalds
2019-01-08 0:08 ` Jonathan Neuschäfer [this message]
2019-01-12 17:14 ` [PATCH v2] kernel/sys.c: Clarify that UNAME26 does not generate unique versions anymore Jonathan Neuschäfer
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=20190108000854.GD3987@latitude \
--to=j.neuschaefer@gmx.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gorcunov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yuehaibing@huawei.com \
/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