2.6.32-696.3.2.el6.x86_64 bad kernel patch?

[Skywalker1957]

I recently patched from OEL 2.6.32-696.3.1.el6.x86_64 to 2.6.32-696.3.2.el6.x86_64 and it broke my application on my server. I had to boot off the old kernel to get my application functioning again. I found the following links online about it, has anyone else run into a problem with this release?

Error documented with CVE-2017-1000364

https://nvd.nist.gov/vuln/detail/CVE-2017-1000364

https://access.redhat.com/security/cve/CVE-2017-1000364

 

[iggsterman]

These are CVE. Vulnerabilities are security risks and should not "break" applications. Maybe your app was built in such a way that it specifically relies on a particular version of the kernel, which is highly unlikely. Another possibility is that the patching went wrong.

 

[Skywalker1957]

No it wasn't. It's repeatable. It completely broke Veritas Netbackup and caused it to core dump. The only other document I can find is here.

https://bugs.centos.org/view.php?id=13453

 

[Skywalker1957]

Here's the error messages I received from it...

Netbackup version 7.7.3

Policies in activity monitor:
Getting error code 40's and failing before they run on vcenter

nbdiscover -noxmloutput -policy <policy name> -includedonly
# # A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007fac7ce23bde, pid=66386, tid=140379615614752 # #
JRE version: (8.0_31-b13) (build ) # Java VM: Java HotSpot(TM) 64-Bit
Server VM (25.31-b07 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# j java.lang.Object.<clinit>()V+0
#
# Core dump written. Default location: /root/backup_work_dir/core or
core.66386
#
# An error report file with more information is saved as:
# /root/backup_work_dir/hs_err_pid66386.log
#
# If you would like to submit a bug report, please visit:
# Caution-

http://bugreport.java.com/bugreport/crash.jsp

#
Aborted (core dumped)

OS (uname -a)
Linux <hostname> 2.6.32-696.3.2.el6.x86_64 #1 SMP Mon Jun 19 11:55:55 PDT
2017 x86_64 x86_64 x86_64 GNU/Linux

Patches applied: (and rolled back/downgraded)
glibc.i686 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-common.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-devel.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-headers.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
kernel.x86_64 2.6.32-696.3.2.el6 ol6_x86_64_latest
kernel-firmware.noarch 2.6.32-696.3.2.el6 ol6_x86_64_latest
kernel-headers.x86_64 2.6.32-696.3.2.el6 ol6_x86_64_latest

 

[iggsterman]

As a matter of opinion, this looks like defective glibc libs that cause java exceptions, especially if you can reproduce it with this specific update. I'd just not use it. Wait for the next one maybe?

 

[Skywalker1957]

It was definately a kernel bug. Oracle released a new kernel and it's resolved now. Thanks!

Good packages:
glibc.i686 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-common.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-devel.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
glibc-headers.x86_64 2.12-1.209.0.3.el6_9.2 ol6_x86_64_latest
kernel.x86_64 2.6.32-696.6.3.el6 ol6_x86_64_latest
kernel-firmware.noarch 2.6.32-696.6.3.el6 ol6_x86_64_latest
kernel-headers.x86_64 2.6.32-696.6.3.el6 ol6_x86_64_latest