Linux 2.6.20.6
Subsystems (2)
We (the -stable team) are announcing the release of the 2.6.20.6 kernel. This has 2 important fixes that should have been in 2.6.20.5. They are issues that were pointed with 2.6.20.5 patches during its review cycle, but the patch updates were mistakenly dropped. Please accept our apologies for the mistake.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the patch between 2.6.20.5 and 2.6.20.6.
The updated 2.6.20.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.git
and can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/
thanks,
-chris
--------
Makefile | 2 +- crypto/scatterwalk.c | 2 +- include/asm-um/common.lds.S | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Summary of changes from v2.6.20.5 to v2.6.20.6
==============================================
Chris Wright (1):
Linux 2.6.20.6
Herbert Xu (1):
CRYPTO api: Use the right value when advancing scatterwalk_copychunks
Paolo 'Blaisorblade' Giarrusso (1):
uml: fix static linking for real
Makefile +1 -1
@@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 20 -EXTRAVERSION = .5 +EXTRAVERSION = .6 NAME = Homicidal Dwarf Hamster # *DOCUMENTATION*
crypto/scatterwalk.c +1 -1
@@ -91,7 +91,7 @@ void scatterwalk_copychunks(void *buf, struct scatter_walk *walk,memcpy_dir (buf, vaddr, len_this_page, out);scatterwalk_unmap (vaddr, out); -scatterwalk_advance (walk, nbytes); +scatterwalk_advance (walk, len_this_page);if (nbytes == len_this_page)break ;
include/asm-um/common.lds.S +1 -1
@@ -15,7 +15,7 @@ PROVIDE (_unprotected_end = .); . = ALIGN(4096); - .note : { *(note.*) } + .note : { *(.note.*) } __start___ex_table = .; __ex_table : { *(__ex_table) } __stop___ex_table = .;
Quoted 8 lines · Chris Wright
We (the -stable team) are announcing the release of the 2.6.20.6 kernel. This has 2 important fixes that should have been in 2.6.20.5. They are issues that were pointed with 2.6.20.5 patches during its review cycle, but the patch updates were mistakenly dropped. Please accept our apologies for the mistake.
The diffstat and short summary of the fixes are below.
Quoted 8 lines
I'll also be replying to this message with a copy of the patch between 2.6.20.5 and 2.6.20.6.
The updated 2.6.20.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.gitand can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/
That tree is not up-to-date. So much for using it to track -stable -- what should I use instead?
Quoted 12 lines · Chuck Ebbert
Quoted 11 lines · Chris Wright
We (the -stable team) are announcing the release of the 2.6.20.6 kernel. This has 2 important fixes that should have been in 2.6.20.5. They are issues that were pointed with 2.6.20.5 patches during its review cycle, but the patch updates were mistakenly dropped. Please accept our apologies for the mistake.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the patch between 2.6.20.5 and 2.6.20.6.
Quoted 8 lines
Quoted 5 lines
The updated 2.6.20.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.gitand can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/That tree is not up-to-date. So much for using it to track -stable -- what should I use instead?
It is the stable-queue tree that's not up-to-date:
http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=summary
Apparently updates stopped three days ago...
Quoted 1 line · * Chuck Ebbert ([email protected]) wrote:
It is the stable-queue tree that's not up-to-date:
Ah, yes that is updated (but only within the last half-hour or so).
Quoted 2 lines · * Chuck Ebbert ([email protected]) wrote:
That tree is not up-to-date. So much for using it to track -stable -- what should I use instead?
It's updated, perhaps you hit a stale mirror?