Skip to contentSkip to conversation

Linux 2.6.16.47-rc1

DISCUSSION Adrian Bunk 2 participants 3 messages Apr 11, 2007

lore
Share & tools
lore
#0 lore raw

Security fixes since 2.6.16.46:
- CVE-2007-1357: APPLETALK: Fix a remotely triggerable crash

Location:
ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/

git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git

RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=rss

Changes since 2.6.16.46:

Adrian Bunk (1):

      Linux 2.6.16.47-rc1

Al Viro (1):

      b44: src_desc->addr is little-endian

Alan Cox (1):
ide-floppy: Fix unformatted media crash

David Moore (1):

      ieee1394: video1394: DMA fix

David S. Miller (1):
[VIDEO] ffb: Fix two DAC handling bugs.

Eric W. Biederman (1):
Fix reparenting to the same thread group. (take 2)

Jean Delvare (1):
APPLETALK: Fix a remotely triggerable crash (CVE-2007-1357)

Jeff Garzik (1):

      [netdrvr] tulip, de2104x: fix typo: s/__sparc_/__sparc__/

Patrick McHardy (1):
[IFB]: Fix crash on input device removal

Sergei Shtylyov (1):
siimage: PIO1/2 taskfile transfer overclocking fix

Stephen Hemminger (1):
tcp: fix cubic scaling error

Thomas Gleixner (3):
prevent timespec/timeval to ktime_t overflow fix MTIME_SEC_MAX on 32-bit
hrtimer: prevent overrun DoS in hrtimer_forward()

 Makefile                       |    2 
 drivers/ide/ide-floppy.c       |    3 -
 drivers/ide/pci/siimage.c      |   59 +++++++++++------------
 drivers/ieee1394/video1394.c   |    8 +++
 drivers/net/b44.c              |    2 
 drivers/net/ifb.c              |   35 +++++--------
 drivers/net/tulip/de2104x.c    |    2 
 drivers/net/tulip/tulip_core.c |    2 
 drivers/video/ffb.c            |   84 +++++++++++++++++++++++----------
 include/linux/ktime.h          |   11 +++-
 include/linux/skbuff.h         |    5 +
 include/net/pkt_cls.h          |    7 +-
 kernel/exit.c                  |   29 +++++++----
 kernel/hrtimer.c               |    6 ++
 net/appletalk/ddp.c            |    7 +-
 net/core/dev.c                 |    8 +--
 net/core/skbuff.c              |    2 
 net/ipv4/tcp_cubic.c           |    6 +-
 net/sched/act_mirred.c         |    2 
 19 files changed, 172 insertions(+), 108 deletions(-)
#1 lore raw

Hi Adrian,

first front off: thanks for the phantastic 2.6.16 stable maintenance.

Currently I wonder if you have any plan for doing the 2.6.16 review for let's say "years", or if you "soon" pick some new series such as 2.6.20 or so for long-term maintenance.

I ask because I wonder if I should wait a bit with a production 2.6.17 kernel line I maintain right now for just one installation base, if you choose some 2.6.2x I can hop on, or whether it is wiser to just downdate this series and profit from the "long-term" 2.6.16 maintenance that is no fun to replicate for 2.6.17 just for this one install pool ...

Thanks in advance,

Signature · 3 lines
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name
  +49 (0)30 / 255 897 45
#2 lore raw
Quoted 1 line · Rene Rebe

Hi Adrian,

Hi René,

Quoted 5 lines

first front off: thanks for the phantastic 2.6.16 stable maintenance.

Currently I wonder if you have any plan for doing the 2.6.16 review for let's say "years", or if you "soon" pick some new series such as 2.6.20 or so for long-term maintenance.

I'm not yet decided whether I'll do the same for some future kernel, but even if I'll do it, that wouldn't imply an immediate dropping of the 2.6.16 series - especially since in a "security fixes only" mode maintaining it would require nearly zero work.

Quoted 5 lines

I ask because I wonder if I should wait a bit with a production 2.6.17 kernel line I maintain right now for just one installation base, if you choose some 2.6.2x I can hop on, or whether it is wiser to just downdate this series and profit from the "long-term" 2.6.16 maintenance that is no fun to replicate for 2.6.17 just for this one install pool ...

If I'll maintain a more recent kernel series, that would be >= 2.6.22. So if you need something in the near future that wouldn't help you.

If 2.6.16 works for you that sounds like a good option, otherwise you could get security support [1] by building upon some distribution kernel (e.g. Ubuntu 6.10 that will get security updates for the next 12 months ships with a 2.6.17 kernel).

Quoted 1 line

Thanks in advance,

cu
Adrian

[1] and that's what the "long-term maintenance" of 2.6.16 is really
about: no regressions and security fixes

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed