From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.37.1
Date: Sun, 19 Apr 2009 19:00:44 +0000 [thread overview]
Message-ID: <20090419190044.GA1493@hera.kernel.org> (raw)
Hello,
As there have been a few minor fixes pending for a while now, I thought
it was time to release 2.4.37.1. Most of these fixes concern minor
security issues which have been backported from 2.6 (mostly local DoSes).
In my opinion, only people with local users might consider upgrading, if
those people still exist !
The patch and changelog will appear soon at the following locations:
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/patch-2.4.37.1.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.37.1
Git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.37.y.git
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.37.y.git
Git repository through the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.4.37.y.git
Reminder for those who are still unaware of it : 2.6.27 will be maintained
for years and is already quite stable. If you're still running 2.4 without
any particular reason, please give 2.6.27-stable a try and report any
regression, should you face any.
Regards,
Willy
--
Summary of changes from v2.4.37 to v2.4.37.1
============================================
Alan Cox (1):
af_rose/x25: Sanity check the maximum user frame size
Oleg Nesterov (2):
exit_notify: kill the wrong capable(CAP_KILL) check
copy_process: fix CLONE_PARENT && parent_exec_id interaction
Serge E. Hallyn (1):
CAP_FS_MASK: add CAP_LINUX_IMMUTABLE and CAP_MKNOD
Willy Tarreau (4):
ATM: ensure we don't listen twice on a socket
scripts: backport checkpatch.pl from mainline 2.6
net: Fix soft lockups/OOM issues w/ unix garbage collector (CVE-2008-5300)
Change VERSION to 2.4.37.1
reply other threads:[~2009-04-19 19:00 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=20090419190044.GA1493@hera.kernel.org \
--to=wtarreau@hera.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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