Changes

Jump to: navigation, search

Download/kernel/rhel6-testing/042stab072.2/changes

1,054 bytes added, 23:14, 24 December 2012
it's now 072.2, added 071 to 072 changes
== Changes ==
This <!-- 071.1 is a merge between 068.8 and 070.11 kernels, adding the features of 068.8 into 070.11 kernel, plus some bug fixes on top of that.-->
Since {{kernel link|rhel6-testing|042stab070.11}}:
<!-- This is a merge between 068* Rebase to RHEL6.3 kernel 2.x branch and 0706.x branch32-279. 07119.1 kernel contains all patches from 068.8 el6 (security and 070.12 kernels. -->bug fixes, see link below)
<!-- 065.5 -->
<!-- 065.6 -->
* [mm] a panic while using huge tables has been fixed (PSBM-17315)
<!-- 071.2 -->
* [media/rc] a possible kernel panic on "rc-core" module unload has been fixed
* [fs/epoll] spurious lockdep warnings has been eliminated
* [mm/hugepages] hugepages are now accounted inside a CT (to kmemsize and lockedpages) (PSBM-17327)
* [ubc] swap failcounters should not be incremented in case of non fatal shortage
* [mm] a new formula has been implemented for pagecache reclaimer (PSBM-15799)
* [ubc] fix BUG due to sleep-in-atomic in set_gang_limits()
* [mm] limit the CT memory portion by its commitment. In simple words: if you have single 256mb container on 1gb machine it's portion should be 256m, not 1gb.
* [mm] set commitment to 0 for unlimited containers. For vmscan priorities that means that their effective memory portion is exactly equal to memory usage and give no bonuses for eliminating penalties for aged pages.
* [cpt] make vzreboot be able to work with new vSwap implementation (without necessity of physical swap) (PSBM-17124)
* [ploop] fix lockdep complains about bd_full acquiring (PSBM-13653)
<!-- 072.1: rebase to 2.6.32-279.19.1.el6 -->
 
<!-- 072.2 -->
* [mm] do not force scanning top priority lru vectors, this could result into forced push anon memory to swap (PSBM-17443)
* [mm] struct gang size decreased to 16Kb, this should eliminate often memory allocation failures on CT start (PSBM-17433)
* [fs] CT O_DIRECT and fsync settings checks have been corrected (PSBM-17157)
* [pfcache] fix using uninitialized data on pfcache mounting
 
=== See also ===
* {{RHSA|2012-1580}}

Navigation menu