linux-kernel - Re: [GIT] kbuild fixes for 3.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTikb0=CvTbN_njhq7JyJwOigEa0eLA@mail.gmail.com>
Date:	Fri, 10 Jun 2011 16:06:01 +0100
From:	Andy Whitcroft <apw@...onical.com>
To:	Ray Lee <ray-lk@...rabbit.org>
Cc:	Arnaud Lacombe <lacombar@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>, pefoley2@...izon.net,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	apw@...onical.com
Subject: Re: [GIT] kbuild fixes for 3.0

On Fri, Jun 10, 2011 at 6:53 AM, Ray Lee <ray-lk@...rabbit.org> wrote:
> On Thu, Jun 9, 2011 at 10:16 PM, Arnaud Lacombe <lacombar@...il.com> wrote:
>> Beside that, no matter what, you are about to break
>> `/usr/sbin/sensors-detect' (from my Fedora 14), which rely on a 3
>> digits version number:
>
> Is there really any compelling technical reason to _not_ have Linus
> release the kernels with a superfluous .0 on the end, with the
> understanding that the -stable team gets to increment it for their
> future releases? It'd make every kernel.org release exactly three
> dotted decimals from here on out, which certainly simplifies things.
>
> It seems like we're just borrowing trouble here by trying to drop it
> down to two numbers.
>
> (Not, mind you, that I give a damn at all one way or the other, but it
> feels like you all are going to be spending a lot of time tripping
> over poor assumptions in userspace rather than doing actual work.)

As an experiment I have uploaded a 3.0 reporting kernel into Ubuntu
Oneiric.  So far we have had issues with:

 - depmod -- (as above)
 - procps (ps/top) -- reporting errors on startup
 - glibc version checks are preventing upgrade of that package

I am sure there will be others, but the last one above has me cornered
at the moment.  Cirtainly we can fix all of these but we are not going
to make it easy for people with un-upgraded userspace if my experience
is anything to go by.

-apw
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/