Linux 2.4.29-hf8

[Willy Tarreau]

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.


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