Last month I wrote about a problem I saw with scsi_id and UDEV in OL5.8. As it screwed up all my UDEV rules is was a pretty important issue for me. It turned out this was due to a mainline security fix (CVE-2011-4127) affecting the latest kernels of both RHEL/OL5 and RHEL/OL6. The comments on the previous post show a couple of workarounds.
Over the weekend I started to update a couple of articles that mentioned UDEV rules (here and here) and noticed the problem had dissapeared. I updated two VMs (OL5.8 and OL6.2) with the latest changes, including the UEK updates and ran the tests again and here’s what I got.
# cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.8 (Tikanga) # uname -r 2.6.39-100.6.1.el5uek # scsi_id -g -u -s /block/sda/sda1 SATA_VBOX_HARDDISK_VB535d493d-7a44eb0f_ # # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.2 (Santiago) # uname -r 2.6.39-100.6.1.el6uek.x86_64 # /sbin/scsi_id -g -u /dev/sda1 1ATA_VBOX_HARDDISK_VB2b5dc561-4ae6e154 #
So it looked like normal service had been resumed. Unfortunately, the MOS Note 1438604.1 associated with this issue is still not public, so I couldn’t tell if this was a unilateral change in UEK, or part of a mainline fix for the previous change.
To check I fired up a CentOS 6.2 VM with the latest kernel updates and switched an Oracle Linux VM to the latest RHEL compatible kernel and did the test on both. As you can see, they both still don’t report the scsi_id for partitions.
# cat /etc/redhat-release CentOS release 6.2 (Final) # uname -r 2.6.32-220.13.1.el6.x86_64 # /sbin/scsi_id -g -u /dev/sda1 # # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.2 (Santiago) # uname -r 2.6.32-220.13.1.el6.x86_64 # /sbin/scsi_id -g -u /dev/sda1 #
It could be the associated fix has not worked through the mainline to RHEL and CentOS yet. I’ll do a bit of digging around to see what is going on here.