Linux 2.4.30-hf1

[Willy Tarreau <wtarreau@exosec.fr>]

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/