LWN: Comments on "Stable kernel updates"

marking known security fix as such

spender — Tue, 21 Sep 2010 12:06:43 +0000

You must be new here.

Some reading material:
http://lwn.net/Articles/373581/
http://lwn.net/Articles/306365/
http://lwn.net/Articles/290227/
http://lwn.net/Articles/297366/
http://lwn.net/Articles/118952/
http://lwn.net/Articles/375335/
http://lwn.net/Articles/402328/
http://lwn.net/Articles/404043/
http://lwn.net/Articles/285438/
http://lwn.net/Articles/286263/
http://lwn.net/Articles/290308/

That should be enough to get you started.

-Brad

marking known security fix as such

Trou.fr — Tue, 21 Sep 2010 10:50:03 +0000

I thought the current policy was to mark *known* fixes with CVE as such in the changelog. Has it changed ?

The 32bit compatibility issue has been actively exploited and not a single word about it in the announcement...

Stable kernel updates

epa — Tue, 21 Sep 2010 10:08:14 +0000

Intermittent double-execution of completely arbitrary instructions. How the hell Al managed to debug *that* I have no idea, but I imagine it would make a good fireside story.

Only at Halloween, I suggest.

Stable kernel updates

nix — Tue, 21 Sep 2010 10:04:45 +0000

Oh no, this sort of story is only any good if Al tells it. He has a gift for this sort of thing.

Stable kernel updates

jengelh — Tue, 21 Sep 2010 09:44:08 +0000

Perhaps you would find spending time with 2.4.37 even more enlightning.

Stable kernel updates

dlang — Tue, 21 Sep 2010 03:33:09 +0000

the question was asked on linux-kernel and Greg answered that the unified tree isn't managed by him, it's created by scripts on kernel.org. He suggested asking the kernel.org managers.

there hasn't been a further response to that.

Stable kernel updates

hmh — Tue, 21 Sep 2010 02:45:18 +0000

Well, the unified stable tree repository is good for a lot of things, but getting low latency updates is not one of them, at least not at this time.

Unfortunately.

Stable kernel updates

malefic — Tue, 21 Sep 2010 02:16:09 +0000

I meant the unified stable git repository. Although, I can see it in the dedicated 2.6.35.y tree. I'm used to getting kernel updates from the former repo, that's why I asked.

Stable kernel updates

pr1268 — Tue, 21 Sep 2010 02:09:05 +0000

Not too sure what you're asking... All the updated kernels listed above are available on kernel.org (as of Tue Sep 21 02:07:50 UTC 2010).

Stable kernel updates

roelofs — Tue, 21 Sep 2010 02:02:04 +0000

How the hell Al managed to debug *that* I have no idea, but I imagine it would make a good fireside story.)

Heck, it would make a good Kernel-page (or Security-page?) story. Hint hint, Jon/Jake ...

Greg

Stable kernel updates

malefic — Tue, 21 Sep 2010 01:51:13 +0000

Is there a reason this hasn't been pushed to kernel.org stable repository?

Stable kernel updates

gregkh — Tue, 21 Sep 2010 00:31:19 +0000

Jon is right, it is getting old, but it's still kicking, so don't declare
it dead yet :)

Where's Og?

nix — Tue, 21 Sep 2010 00:17:55 +0000

Security *fix* in this release, that is.

Where's Og?

nix — Tue, 21 Sep 2010 00:17:32 +0000

Well, the ptrace-compat security hole in this release is clearly proof that 'the best-laid plans o' mice and men gang aft ogley'.

Stable kernel updates

ris — Tue, 21 Sep 2010 00:13:17 +0000

My apologies. I remembered reading http://lwn.net/Articles/402512/
"(though 2.6.27 is clearly reaching the end of the line)" and jumped the gun.

Where's Og?

jd — Tue, 21 Sep 2010 00:03:00 +0000

We want more tales of Og! Whilst Greg is probably too busy to do this, there really should be an Og web comic - a Dilbert/UserFriendly but aimed at kernel developers.

Having said that, excellent work on a new release.

Stable kernel updates

nix — Mon, 20 Sep 2010 23:52:01 +0000

Yes, and the fairly nasty HPET timer bug which torpedoed my systems and many others (all so far known running Intel ICH10 chipsets, but I'm sure there are other affected ones out there). (It's only 'fairly nasty' because its side-effects are obvious -- slowdown to halt or insane timing -- while the ARM bug Al Viro spotted, now that was very, very nasty. Intermittent double-execution of completely arbitrary instructions. How the hell Al managed to debug *that* I have no idea, but I imagine it would make a good fireside story.)

Stable kernel updates

linuxrocks123 — Mon, 20 Sep 2010 23:49:05 +0000

H. Peter Anvin (2):
x86-64, compat: Test %rax for the syscall number, not %eax
compat: Make compat_alloc_user_space() incorporate the access_ok()

I assume this means that this update fixes the very, very nasty x86-64 exploit (re)-discovered a few days ago?

---linuxrocks123

Stable kernel updates

gregkh — Mon, 20 Sep 2010 23:16:23 +0000

Where did I say that the .27-stable series is not going to be maintained much longer?