Linux 2.6.16.4
We (the -stable team) are announcing the release of the 2.6.16.4 kernel.
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.16.3 and 2.6.16.4, as it is small enough to do so.
The updated 2.6.16.y git tree can be found at:
rsync://rsync.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 +- kernel/signal.c | 1 - 2 files changed, 1 insertion(+), 2 deletions(-)
Summary of changes from v2.6.16.3 to v2.6.16.4
==============================================
Greg Kroah-Hartman:
Linux 2.6.16.4
Oleg Nesterov:
RCU signal handling [CVE-2006-1523]
Makefile +1 -1
@@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 16 -EXTRAVERSION = .3 +EXTRAVERSION = .4 NAME=Sliding Snow Leopard # *DOCUMENTATION*
kernel/signal.c +0 -1
@@ -975,7 +975,6 @@ __group_complete_signal(int sig, structif (t ==NULL )/* restart balancing at this thread */ t = p->signal->curr_target = p; -BUG_ON (t->tgid != p->tgid);while (!wants_signal (sig, t)) { t =next_thread (t);
Re: several messages
In reply to Greg KHQuoted 10 lines
Date: Tue, 11 Apr 2006 09:26:20 -0700
Subject: Linux 2.6.16.3
David Howells:
Keys: Fix oops when adding key to non-keyring [CVE-2006-1522]Date: Tue, 11 Apr 2006 10:33:23 -0700
Subject: Linux 2.6.16.4
Oleg Nesterov:RCU signal handling [CVE-2006-1523]
Now admins spend another hour this day just to upgrade. These two patches could have been queued until the end of the day. Maybe another one turns up soon.
Jan Engelhardt
Re: several messages
Hello, Jan Engelhardt.
On 11.04.2006 23:04 you said the following:
Quoted 1 line
Now admins spend another hour this day just to upgrade.
It's admin's job, isn't it?
Quoted 2 lines
These two patches could have been queued until the end of the day. Maybe another one turns up soon. Jan Engelhardt
Hmm... Interesting. Are you blaming security officers for doing their job? Please, don't! And many many thanks to Greg for giving us security patches as soon as possible.
Signature · 3 lines
Boris B. Zhmurov mailto: [email protected] "wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
Re: several messages
In reply to Jan EngelhardtQuoted 6 lines · Jan Engelhardt
Quoted 5 lines
Date: Tue, 11 Apr 2006 09:26:20 -0700
Subject: Linux 2.6.16.3
David Howells:
Keys: Fix oops when adding key to non-keyring [CVE-2006-1522]
Quoted 8 lines
Quoted 4 lines
Date: Tue, 11 Apr 2006 10:33:23 -0700
Subject: Linux 2.6.16.4
Oleg Nesterov:RCU signal handling [CVE-2006-1523]Now admins spend another hour this day just to upgrade. These two patches could have been queued until the end of the day. Maybe another one turns up soon.
The first one went out last night, as it was a real issue that affected people and I had already waited longer than I felt comfortable with, due to travel issues I had (two different talks in two different cities in two different days.)
The second one went out today, because it was reported today. Should I have waited until tomorrow to see if something else came up?
thanks,
greg k-h
Re: several messages
Quoted 9 lines
The first one went out last night, as it was a real issue that affected people and I had already waited longer than I felt comfortable with, due to travel issues I had (two different talks in two different cities in two different days.)
The second one went out today, because it was reported today. Should I have waited until tomorrow to see if something else came up?
No of course not, I did not know the first one was already due long time.
[Sigh, pine changed the subject header and I did not notice.]
Jan Engelhardt
Re: several messages
In reply to Greg KHOn 11 Apr 2006, Greg KH whispered secretively:
Quoted 7 lines
The first one went out last night, as it was a real issue that affected people and I had already waited longer than I felt comfortable with, due to travel issues I had (two different talks in two different cities in two different days.)
The second one went out today, because it was reported today. Should I have waited until tomorrow to see if something else came up?
Indeed.
On top of that, they're `only' local DoSes, so many admins (i.e. those without untrusted local users) will probably not have installed .3 yet:
and anyone with untrusted local users probably has someone whose entire job is handling security anyway.
There's nothing wrong with rapid-fire -stables; either the issue is (in the judgement of the ones doing the installation) critical, in which case it should get out as fast as possible, or it isn't, in which case the local installing admins can put it off for a day or so themselves to see if another release comes out immediately afterwards.
Signature · 3 lines
`On a scale of 1-10, X's "brokenness rating" is 1.1, but that's only because bringing Windows into the picture rescaled "brokenness" by a factor of 10.' --- Peter da Silva