From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jon DeVree <nuxi@vault24.org>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] kernel/sys.c: Fix UNAME26 for 4.0
Date: Mon, 23 Feb 2015 20:05:12 +0100 [thread overview]
Message-ID: <20150223190512.GC823@two.firstfloor.org> (raw)
In-Reply-To: <20150223110041.eaa2d7e6e1e54e11e1f9e945@linux-foundation.org>
On Mon, Feb 23, 2015 at 11:00:41AM -0800, Andrew Morton wrote:
> On Mon, 23 Feb 2015 00:43:12 -0500 Jon DeVree <nuxi@vault24.org> wrote:
>
> > --- a/kernel/sys.c
> > +++ b/kernel/sys.c
> > @@ -1127,7 +1127,7 @@ static int override_release(char __user *release, size_t len)
> > break;
> > rest++;
> > }
> > - v = ((LINUX_VERSION_CODE >> 8) & 0xff) + 40;
> > + v = ((LINUX_VERSION_CODE >> 8) & 0xff) + 60;
> > copy = clamp_t(size_t, len, 1, sizeof(buf));
> > copy = scnprintf(buf, copy, "2.6.%u%s", v, rest);
> > ret = copy_to_user(release, buf, copy + 1);
>
> Huh.
>
> I wonder if we still need this.
I think so. A lot of the world is still stuck on RHEL6 ...
And compatbility to old binaries is a high value.
The original program I needed it for is fixed however.
-Andi
>
>
>
> We should update the comment:
>
> --- a/kernel/sys.c~kernel-sysc-fix-uname26-for-40-fix
> +++ a/kernel/sys.c
> @@ -1108,6 +1108,7 @@ DECLARE_RWSEM(uts_sem);
> /*
> * Work around broken programs that cannot handle "Linux 3.0".
> * Instead we map 3.x to 2.6.40+x, so e.g. 3.0 would be 2.6.40
> + * And we map 4.x to 2.6.60+x, so 4.0 would be 2.6.60.
> */
> static int override_release(char __user *release, size_t len)
> {
>
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2015-02-23 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 5:43 [PATCH] kernel/sys.c: Fix UNAME26 for 4.0 Jon DeVree
2015-02-23 19:00 ` Andrew Morton
2015-02-23 19:05 ` Andi Kleen [this message]
2015-02-27 23:31 ` Matt Mullins
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=20150223190512.GC823@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuxi@vault24.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