lkml.org 
[lkml]   [2021]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Kernel version numbers after 4.9.255 and 4.4.255
Hi!

> > > Ugh, I thought this was an internal representation, not an external one
> > > :(
> > >
> > > > It might work somewhere, but there are a lot of (X * 65536 + Y * 256 + Z)
> > > > assumptions all around the world. So this doesn't look like a good idea.
> > >
> > > Ok, so what happens if we "wrap"? What will break with that? At first
> > > glance, I can't see anything as we keep the padding the same, and our
> > > build scripts seem to pick the number up from the Makefile and treat it
> > > like a string.
> > >
> > > It's only the crazy out-of-tree kernel stuff that wants to do minor
> > > version checks that might go boom. And frankly, I'm not all that
> > > concerned if they have problems :)
> > >
> > > So, let's leave it alone and just see what happens!
> >
> > Yeah, stable is a great place to do the experiments. Not that this is
> > the first time :-(.
>
> How else can we "test this out"?
>
> Should I do an "empty" release of 4.4.256 and see if anyone complains?

It seems that would be bad idea, as it would cause problems when stuff
is compiled on 4.4.256, not simply by running it.

Sasha's patch seems like one option that could work.

Even safer option is to switch to 4.4.255-st1, 4.4.255-st2 ... scheme.

Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2021-02-05 19:49    [W:22.667 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site