Linux 2.6.16.25

Linux 2.6.16.25

[Greg KH]

We (the -stable team) are announcing the release of the 2.6.16.25 kernel.

I'll also be replying to this message with a copy of the patch between
2.6.16.24 and 2.6.16.25, 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 |    1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

Summary of changes from v2.6.16.24 to v2.6.16.23
================================================

Greg Kroah-Hartman:
      Linux 2.6.16.25

Linus Torvalds:
      Fix nasty /proc vulnerability (CVE-2006-3626)

Re: Linux 2.6.16.25

[Greg KH]

diff --git a/Makefile b/Makefile
index 9b1622f..84166a1 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
 VERSION = 2
 PATCHLEVEL = 6
 SUBLEVEL = 16
-EXTRAVERSION = .24
+EXTRAVERSION = .25
 NAME=Sliding Snow Leopard
 
 # *DOCUMENTATION*
diff --git a/fs/proc/base.c b/fs/proc/base.c
index c192cb2..9d99674 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -1366,6 +1366,7 @@ static int pid_revalidate(struct dentry 
 		} else {
 			inode->i_uid = 0;
 			inode->i_gid = 0;
+			inode->i_mode = 0;
 		}
 		security_task_to_inode(task, inode);
 		return 1;

Re: [stable] Linux 2.6.16.25

[Greg KH]

On Fri, Jul 14, 2006 at 07:59:06PM -0700, Greg KH wrote:
> We (the -stable team) are announcing the release of the 2.6.16.25 kernel.

Oops, please note that we now have some reports that this patch breaks
some versions of HAL.  So if you're relying on HAL, you might not want
to use this fix just yet (please evaluate the risks of doing this on
your own.)

Note that HAL usually does not run on servers, so this should be safe
there.  We'll try to provide a better fix soon...

Sorry about this.

greg k-h

Re: [stable] Linux 2.6.16.25

[Pavel Machek]

Hi!

> > We (the -stable team) are announcing the release of the 2.6.16.25 kernel.
> 
> Oops, please note that we now have some reports that this patch breaks
> some versions of HAL.  So if you're relying on HAL, you might not want
> to use this fix just yet (please evaluate the risks of doing this on
> your own.)
> 
> Note that HAL usually does not run on servers, so this should be safe
> there.  We'll try to provide a better fix soon...

So there's going to be one more 2.6.16, good.

Did you receive that fix-pdflush-after-wakeup? I believe I mailed it
to stable@kernel.org, but I got no reply...
						Pavel

-- 
Thanks for all the (sleeping) penguins.

Re: [stable] Linux 2.6.16.25

[Pavel Machek]

Hi!

On Thu 01-01-70 13:26:35, Pavel Machek wrote:

...and sorry for another mail from 1970. Sharp Zaurus sl3000c is very
nice machine, but its RTC certainly sucks.

							Pavel

-- 
Thanks for all the (sleeping) penguins.

Re: [stable] Linux 2.6.16.25

[Greg KH]

On Thu, Jan 01, 1970 at 01:26:35PM +0000, Pavel Machek wrote:
> Hi!
> 
> > > We (the -stable team) are announcing the release of the 2.6.16.25 kernel.
> > 
> > Oops, please note that we now have some reports that this patch breaks
> > some versions of HAL.  So if you're relying on HAL, you might not want
> > to use this fix just yet (please evaluate the risks of doing this on
> > your own.)
> > 
> > Note that HAL usually does not run on servers, so this should be safe
> > there.  We'll try to provide a better fix soon...
> 
> So there's going to be one more 2.6.16, good.

Already went out :)

> Did you receive that fix-pdflush-after-wakeup? I believe I mailed it
> to stable@kernel.org, but I got no reply...

Yes, it's in our queue.  Did you want that for 2.6.16 or 2.6.17?  I
assumed .17.

thanks,

greg k-h

Re: [stable] Linux 2.6.16.25

[Pavel Machek]

Hi!

> > So there's going to be one more 2.6.16, good.
> 
> Already went out :)
> 
> > Did you receive that fix-pdflush-after-wakeup? I believe I mailed it
> > to stable@kernel.org, but I got no reply...
> 
> Yes, it's in our queue.  Did you want that for 2.6.16 or 2.6.17?  I
> assumed .17.

Aha, I wanted it in .16 -- because that's what suse uses. OTOH it
probably makes sense to queue it for both....

							Pave

-- 
Thanks, Sharp!

Re: Linux 2.6.16.25

[Bill Davidsen]

Greg KH wrote:
> We (the -stable team) are announcing the release of the 2.6.16.25 kernel.
> 
> I'll also be replying to this message with a copy of the patch between
> 2.6.16.24 and 2.6.16.25, as it is small enough to do so.

Why does the patch make it to linux-kernel-announce and the nice 
announcement, like this one, not? The short patch description is far 
more useful, since if it's to something I don't use I don't need to 
apply or examine it.
> 
> 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 |    1 +
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> Summary of changes from v2.6.16.24 to v2.6.16.23
> ================================================
> 
> Greg Kroah-Hartman:
>       Linux 2.6.16.25
> 
> Linus Torvalds:
>       Fix nasty /proc vulnerability (CVE-2006-3626)
> 


-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.

Re: Linux 2.6.16.25

[Greg KH]

On Tue, Jul 18, 2006 at 05:07:53PM -0400, Bill Davidsen wrote:
> Greg KH wrote:
> >We (the -stable team) are announcing the release of the 2.6.16.25 kernel.
> >
> >I'll also be replying to this message with a copy of the patch between
> >2.6.16.24 and 2.6.16.25, as it is small enough to do so.
> 
> Why does the patch make it to linux-kernel-announce and the nice 
> announcement, like this one, not? The short patch description is far 
> more useful, since if it's to something I don't use I don't need to 
> apply or examine it.

I have no idea how the linux-kernel-announce list works, sorry.  Try
asking the vger.kernel.org owners.

thanks,

greg k-h