[Announce] Kernel RHEL6 testing 042stab065.1

[Kir Kolyshkin]

OpenVZ project has released an updated RHEL6 based
testing kernel. Read below for more information.

NOTE that this is a *testing* kernel, not recommended for production.

Changes
=======
Since 042stab63.2:
* Rebase to 2.6.32-279.14.1.el6 RHEL6.3 kernel (security and bug fixes, 
see RHSA-2012:1426)
* [fuse] fixed use after free in writeback + some cleanup (PSBM-16442)
* [fuse] invalidate_files notification implemented (PSBM-16105)
* [venet] prohibit moving venet device between network namespaces (from 
CT to CT0). This causes net devices renumeration on CT shutdown (#2414)
* [cpt/delayfs] eliminate possible kernel panic in delayfs_preopen() by 
adding a check that fake private is valid before dereferencing (PCLIN-31310)
* [cpt/delayfs] restore mount parameters right after successfull 
remount, thus eliminate possible file opens errors due to temporary 
network/NFS server issues (PCLIN-31286)
* [cpt] eliminate possible kernel panic: do not restart tcp retransmit 
timer in case the queue is empty (#2407)
* [cpt] do not convert errors in m(un)lock() called by cpt code. Not a 
fix, but related to the bug #2404
* [mm] disable by default secure bottom-up lookup for exec areas on ia32 
until Red Hat fixes the bug in fork/exec (PSBM-15942)
* [audit] libc:getlogin() behavior has been fixed on enter/exec inside 
CT (#2402)
* [devtmpfs] devtmpfs permissions were corrected to 0755 if mounting 
inside a CT (PCLIN-31293, #2397)
* [fuse] i_size value for a file not opened yet on the node has been 
corrected (the size from server is reported) (PSBM-15941)
* [perf] evsel: Fix an issue where perf report fails to show
* [jbd2] protect fs metadata on pStorage disaster scenario. It does not 
protect us from userdata corruption, which is a known bug in current PCS 
release. (PSBM-15484)
* [cpt/posix_timers] overrun counter migration support added 
(PSBM-15580, #2324)


Download
========
http://wiki.openvz.org/Download/kernel/rhel6-testing/042stab065.1


Bug reporting
=============
Use http://bugzilla.openvz.org/  to report any bugs found.


Other sources of info on updates
================================
See http://wiki.openvz.org/News  to view all the news (including updates)
online. There you can also find RSS/Atom feed links.


Best regards,
   OpenVZ team