Editing Download/kernel/rhel6/042stab078.22/changes
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 15: | Line 15: | ||
* reworked fsync locking in order to prevent possible node lockups (PSBM-19460) | * reworked fsync locking in order to prevent possible node lockups (PSBM-19460) | ||
* enhanced memory management algorithm to give more priority to containers with unlimited memory barriers set | * enhanced memory management algorithm to give more priority to containers with unlimited memory barriers set | ||
− | * fixed kernel panic on nfs unmount issued inside a container if volume had been mounted on a Hardware Node (PCLIN-31620) | + | * fixed kernel panic on nfs unmount issued inside a container if volume had been mounted on a Hardware Node. |
+ | (PCLIN-31620) | ||
* corrected /proc/stat:btime values on a container after live migration. This should also fix glitches with process start time reports ({{B|2572}}) | * corrected /proc/stat:btime values on a container after live migration. This should also fix glitches with process start time reports ({{B|2572}}) | ||
* fixed issue when container checkpoint/restore cycle could break process capabilities (PSBM-18649) | * fixed issue when container checkpoint/restore cycle could break process capabilities (PSBM-18649) | ||
* fixed issue when under certain conditions direct memory reclaiming could trigger fs-related activity and could cause the Node deadlock in case of high memory pressure (PSBM-20210) | * fixed issue when under certain conditions direct memory reclaiming could trigger fs-related activity and could cause the Node deadlock in case of high memory pressure (PSBM-20210) | ||
* fixed issue when checkpointing a container with a tty under inotify watch could trigger a kernel panic (PCLIN-31849) | * fixed issue when checkpointing a container with a tty under inotify watch could trigger a kernel panic (PCLIN-31849) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== See also === | === See also === |