Editing Download/kernel/rhel6/042stab111.11/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 3: | Line 3: | ||
Since {{kernel link|rhel6|042stab108.8}}: | Since {{kernel link|rhel6|042stab108.8}}: | ||
| − | |||
| − | |||
* ploop could get stuck inside ploop_make_request() causing Node to hang (PSBM-29066, {{OVZ|6293}}, {{OVZ|6392}}) | * ploop could get stuck inside ploop_make_request() causing Node to hang (PSBM-29066, {{OVZ|6293}}, {{OVZ|6392}}) | ||
* Under certain network workload, Container checkpoint/restore operations could result in conntrack duplication which could prevent online migration of said Container (PSBM-32411) | * Under certain network workload, Container checkpoint/restore operations could result in conntrack duplication which could prevent online migration of said Container (PSBM-32411) | ||
| Line 11: | Line 9: | ||
* CPT image compatibility was broken in 042stab108.x kernels. As a result, received but nondelivered TCP packets saved into CPT image could, in certain circumstances, lose TCP flags during restore on 042stab108.x kernels. This resulted in incorrect processing of restored packets and could cause unexpected kernel warnings or lead to issues in userspace applications (PSBM-33549, {{OVZ|6278}}) | * CPT image compatibility was broken in 042stab108.x kernels. As a result, received but nondelivered TCP packets saved into CPT image could, in certain circumstances, lose TCP flags during restore on 042stab108.x kernels. This resulted in incorrect processing of restored packets and could cause unexpected kernel warnings or lead to issues in userspace applications (PSBM-33549, {{OVZ|6278}}) | ||
* Fixed the reason of invalid warning "ida_remove called for id=0 which is not allocated." (PSBM-33789, {{OVZ|6161}}) | * Fixed the reason of invalid warning "ida_remove called for id=0 which is not allocated." (PSBM-33789, {{OVZ|6161}}) | ||
| − | * ploop journal could get stuck in ' | + | * ploop journal could get stuck in 'blockwritefull_page()' causing Node to hang. (PSBM-35095) |
* In certain circumstances, Hardware Nodes with 108.x kernels could crash. (PSBM-37612) | * In certain circumstances, Hardware Nodes with 108.x kernels could crash. (PSBM-37612) | ||
* rsyslogd was not allowed to dump Container-related kernel messages inside Container. ({{OVZ|5774}}) | * rsyslogd was not allowed to dump Container-related kernel messages inside Container. ({{OVZ|5774}}) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
