Linux 2.6.27.51

[Greg KH]

I'm announcing the release of the 2.6.27.51 kernel.  All users of the
2.6.27 kernel series are very strongly encouraged to upgrade.

The updated 2.6.27.y git tree can be found at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git
and can be browsed at the normal kernel.org git web browser:
        http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary

thanks,

greg k-h

------------

 Makefile                 |    2 -
 arch/x86/xen/enlighten.c |    2 -
 arch/x86/xen/time.c      |   43 -----------------------
 arch/x86/xen/xen-ops.h   |    3 +
 drivers/char/nvram.c     |   14 +++++--
 drivers/md/raid10.c      |   18 +++++++++
 drivers/pci/quirks.c     |    1 
 fs/ecryptfs/file.c       |   60 +++++++++++++++++++-------------
 fs/jfs/xattr.c           |   87 ++++++++++++++++++++---------------------------
 fs/signalfd.c            |    2 +
 fs/splice.c              |   12 ------
 mm/backing-dev.c         |    3 +
 12 files changed, 115 insertions(+), 132 deletions(-)

Andrew Morton (1):
      mm/backing-dev.c: remove recently-added WARN_ON()

Dave Kleikamp (1):
      jfs: don't allow os2 xattr namespace overlap with others

Greg Kroah-Hartman (1):
      Linux 2.6.27.51

H. Peter Anvin (1):
      nvram: Fix write beyond end condition; prove to gcc copy is safe

Jeremy Fitzhardinge (1):
      xen: drop xen_sched_clock in favour of using plain wallclock time

Julia Lawall (1):
      fs/ecryptfs/file.c: introduce missing free

Kay Sievers (1):
      bdi: register sysfs bdi device only once per queue

Miklos Szeredi (1):
      splice: fix misuse of SPLICE_F_NONBLOCK

Nathan Lynch (1):
      signalfd: fill in ssi_int for posix timers and message queues

NeilBrown (1):
      md/raid10: fix deadlock with unaligned read during resync

Tejun Heo (1):
      PCI: disable MSI on VIA K8M800

Tyler Hicks (1):
      eCryptfs: Handle ioctl calls with unlocked and compat functions

--
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/