From: Willy Tarreau <wtarreau@exosec.fr>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.29-hf8
Date: Sun, 8 May 2005 00:18:27 +0200 [thread overview]
Message-ID: <20050507221827.GA13611@exosec.fr> (raw)
Hello,
Here comes the eighth hotfix release for kernel 2.4.29. It should be the last
*announced* version, but will silently follow 2.4.30-hf updates. To support
multiple parallel versions, I've inserted a directory level on the site with
the base version number. I prefered risking breaking a few bookmarks now than
adding confusion later. The release is available at usual places :
http://linux.exosec.net/kernel/2.4-hf/
Small changelog below. Nothing critical there.
Regards,
Willy
Changelog From 2.4.29-hf7 to 2.4.29-hf8 (semi-automated)
---------------------------------------
'+' = added ; '-' = removed
+ 2.4.30-panic-if-more-than-one-moxa-1 (David Monniaux)
[PATCH] fix moxa crash with more than one 1 board.
The current Moxa Intellio driver (moxa.c) panics when using > 1 board.
Fixed build by declaring variable prior to usage - Willy.
+ 2.4.30-bonding-rmmod-oops-1 (Mitch Williams)
It fixes a stack dump when unloading the bonding module in 802.3ad mode
if spinlock debugging is turned on, and it was already merged in 2.6.
+ 2.4.29-sk_rmem_alloc-assertion-failure-1 (Herbert Xu)
[NETLINK]: Fix sk_rmem_alloc assertion failure in af_netlink.c.
In netlink_dump we're operating on sk after dropping the cb lock. This is
racy because the owner of the socket could close it after we drop the cb
lock. The solution is to hold a ref count on the socket before we drop the
cb lock.
+ 2.4.30-rwsem-spinlocks-must-disable-interrupts-2 (David Howells)
[PATCH] rwsem: Make rwsems use interrupt disabling spinlocks.
The attached patch makes read/write semaphores use interrupt disabling
spinlocks in the slow path, thus rendering the up functions and trylock
functions available for use in interrupt context. This matches the
regular semaphore behaviour. Typo fixed by Mikael Pettersson.
reply other threads:[~2005-05-07 22:18 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=20050507221827.GA13611@exosec.fr \
--to=wtarreau@exosec.fr \
--cc=linux-kernel@vger.kernel.org \
/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