From: Willy Tarreau <wtarreau@exosec.fr>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.30-hf1
Date: Sun, 8 May 2005 00:25:25 +0200 [thread overview]
Message-ID: <20050507222525.GA23035@exosec.fr> (raw)
Hello,
Here comes the first hotfix release for kernel 2.4.30 :
http://linux.exosec.net/kernel/2.4-hf/
It only contains 4 minor patches. Please check small
changelog below. Only compiled on x86 right now, but
I'm testing it on sparc64 and alpha right now in order
to be confident in the first release.
Regards,
Willy
Changelog From 2.4.30 to 2.4.30-hf1 (semi-automated)
---------------------------------------
'+' = added ; '-' = removed
+ 2.4.30-panic-if-more-than-one-moxa-2 (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.30-madvise-must-return-EIO-1 (Hugh Dickins)
[PATCH] madvise_willneed -EIO beyond EOF.
When the rlim_rss was removed from madvise_willneed, we unintentionally
changed its error when applied to an area wholly beyond end of file: it
used to report -EIO (whereas 2.6 reports success), it currently reports
the confusingly inappropriate -EBADF. Revert to -EIO in that case.
+ 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:25 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=20050507222525.GA23035@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