mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: linux-kernel@vger.kernel.org
Cc: marcelo.tosatti@cyclades.com
Subject: Linux-2.4.31-hf4
Date: Sat, 20 Aug 2005 16:30:19 +0200	[thread overview]
Message-ID: <20050820143019.GA14526@alpha.home.local> (raw)

Hello !

After having accumulated a few weeks delay, the fourth hotfix for kernel
2.4.31 is finally out. It was also the right time to release it now that
the isofs and zlib stories came to an end.

Because of the ZISOFS security fix, users of older -hf or plain 2.4.X
should upgrade either to latest -hf or to 2.4.32-pre3. Other fixes are
less important.

As usual, I've also updated 2.4.29 and 2.4.30. So all 3 Kernels 2.4.29-hf14,
2.4.30-hf7 and 2.4.31-hf4 are available as individual, full, and incremental
patches here:

    http://linux.exosec.net/kernel/2.4/2.4-hf/

The changelog is appended to this mail. I've built 2.4.31-hf4 with all
modules, and nothing more yet, but Grant Coady will soon report the
full build and run test here :

    http://bugsplatter.mine.nu/test/linux-2.4/  (warning! URL changed)

Regards,
Willy

--

Changelog From 2.4.31-hf3 to 2.4.31-hf4
---------------------------------------
'+' = added ; '-' = removed

- 2.4.31-zlib-security-bugs-1                                    (Tim Yamin)
+ 2.4.31-zlib-security-bugs-2                     (Tim Yamin, Sergey Vlasov)

  Reverted the Z_OK to Z_DATA_ERROR changes in inftrees.c (& PPC).

+ 2.4.31-zisofs-check-deflatebound-1                        (Linus Torvalds)

  [PATCH] PATCH: Fix outstanding gzip/zlib security issues
  Add fakey 'deflateBound()' function to the in-kernel zlib routines.
  It's not the real deflateBound() in newer zlib libraries, partly because
  the upcoming usage of it won't have the "stream" available, so we can't
  have the same interfaces anyway. Problem noted by Tim Yamin.

+ 2.4.31-nat-fix-memory-corruption-1                       (Patrick McHardy)

  [NETFILTER]: Fix potential memory corruption in NAT code (aka memory NAT)

+ 2.4.31-isofs-option-parse-fix-1               (Horms + Andrey J.Melnikoff)

  Fix isofs option parser. If iocharset, map or session are matched,
  then none of the if or else if clauses under sbsector will match
  (that is none of these clauses match iocharset, map or session),
  and thus the else clause will be hit, and the function will return
  1 without parsing any furhter options. Also fix gcc-3.4 warnings.

+ 2.4.31-netfilter-tcp-unclean-1.diff                      (Patrick McHardy)

  [NETFILTER]: Ignore PSH on SYN/ACK in ipt_unclean

+ 2.4.31-redblacktree-missing-returns-1              (deep-blue@t-online.de)

  [PATCH] fix RedBlackTree rb_next/rb_prev functions. I have found a
  bug in the source of rbtree.c file in /lib. In Kernel 2.6 it's ok,
  but 2.4.31 has this error. We try to use it with the jffs2 source
  code and only with this fix it works fine.

+ 2.4.31-alpha-cabriolet-needs-ns87312-1                       (Bill Dupree)

  [PATCH] Fix Alpha AXP Cabriolet build. Alpha AXP Cabriolet build
  fails with unresolved reference to ns87312_enable_ide().

-- END --


                 reply	other threads:[~2005-08-20 14:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050820143019.GA14526@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome