linux-kernel - Linux 2.6.27.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081015232950.GA29323@kroah.com>
Date:	Wed, 15 Oct 2008 16:29:50 -0700
From:	Greg KH <gregkh@...e.de>
To:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...nel.org
Subject: Linux 2.6.27.1

We (the -stable team) are announcing the release of the 2.6.27.1
kernel.

It contains one bugfix, disabling CONFIG_DYNAMIC_FTRACE that could cause
memory corruption.  This is believed to be the source of the recent
e1000 hardware b0rkage, and all users of the 2.6.27 kernel series are
encouraged to either disable the option, or to upgrade to this kernel
version which will force you to do so.

I'll also be replying to this message with a copy of the patch between
2.6.27 and 2.6.27.1

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 +-
 kernel/trace/Kconfig |    3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

Greg Kroah-Hartman (1):
      Linux 2.6.27.1

Steven Rostedt (1):
      disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload

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