Linux 2.6.16.26
Subsystems (2)
We (the -stable team) are announcing the release of the 2.6.16.26 kernel.
This should fix the reported issue of NetworkManager dying when using the 2.6.16.25 kernel release. All users of the 2.6.16 kernel are recommended to upgrade to this kernel, as it fixes a publicly known security issue that can provide root access to any local user of the machine.
I'll also be replying to this message with a copy of the patch between 2.6.16.25 and 2.6.16.26, as it is small enough to do so.
The updated 2.6.16.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
and can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/
thanks,
greg k-h
--------
Makefile | 2 +- fs/proc/base.c | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-)
Summary of changes from v2.6.16.25 to v2.6.16.26
================================================
Greg Kroah-Hartman:
Linux 2.6.16.25
Linus Torvalds:
Relax /proc fix a bit
Makefile +1 -1
@@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 16 -EXTRAVERSION = .25 +EXTRAVERSION = .26 NAME=Sliding Snow Leopard # *DOCUMENTATION*
fs/proc/base.c +2 -1
@@ -1366,8 +1366,8 @@ static int pid_revalidate(struct dentry }else { inode->i_uid =0 ; inode->i_gid =0 ; - inode->i_mode =0 ; } + inode->i_mode &= ~(S_ISUID |S_ISGID );security_task_to_inode (task, inode);return 1 ; }
@@ -1395,6 +1395,7 @@ static int tid_fd_revalidate(struct dent inode->i_uid =0 ; inode->i_gid =0 ; } + inode->i_mode &= ~(S_ISUID |S_ISGID );security_task_to_inode (task, inode);return 1 ; }
Quoted 1 line · Greg KH
We (the -stable team) are announcing the release of the 2.6.16.26 kernel.
<snip>
Quoted 2 lines
Greg Kroah-Hartman:
Linux 2.6.16.25
Ick, I mistyped this, too many version changes recently, it really is the 2.6.16.26 release, as the Makefile shows.
And I don't think there's any way to go back and change a git commit message. Or is there?
thanks,
greg k-h
Quoted 5 lines · Greg KH
Quoted 1 line · Greg KH
We (the -stable team) are announcing the release of the 2.6.16.26 kernel.
<snip>
Quoted 8 lines
Quoted 2 lines
Greg Kroah-Hartman:
Linux 2.6.16.25Ick, I mistyped this, too many version changes recently, it really is the 2.6.16.26 release, as the
Makefileshows.And I don't think there's any way to go back and change a git commit message. Or is there?
You would need to git-reset then git-commit, but it's a little bit dirty and my annoy the users who will have already fetched your tree. That does not matter much anyway. I believe that people will understand anyway !
Quoted 3 lines
thanks,
greg k-h
Cheers,
Willy
Quoted 2 lines · Willy Tarreau
You would need to git-reset then git-commit
Actually, these days we suggest doing
git commit --amend
instead to change the top commit if you mis-type something or find a problem.
But, as you point out:
Quoted 2 lines
but it's a little bit dirty
and my annoy the users who will have already fetched your tree.
Indeed. Something that has already been exported should _not_ be amended, because it generates a whole new commit, and people who have already gotten the old one would be unhappy.
Linus
Quoted 11 lines · Linus Torvalds
Quoted 2 lines · Willy Tarreau
You would need to git-reset then git-commit
Actually, these days we suggest doing
git commit --amendinstead to change the top commit if you mis-type something or find a problem.
Quoted 8 lines
But, as you point out:
Quoted 2 lines
but it's a little bit dirty
and my annoy the users who will have already fetched your tree.Indeed. Something that has already been exported should _not_ be amended, because it generates a whole new commit, and people who have already gotten the old one would be unhappy.
Yes, I'll just live with it and remember this for next time.
thanks,
greg k-h