Discuss March 2023

discuss@lists.centos.org

23 participants
22 discussions

CentOS-announce Digest, Vol 212, Issue 1
by centos-announce-request＠centos.org 02 Mar '23

02 Mar '23

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2023:0978 Important CentOS 7 git Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 1 Mar 2023 14:01:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2023:0978 Important CentOS 7 git Security Update Message-ID: <20230301140143.GA29553(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2023:0978 Important Upstream details at : https://access.redhat.com/errata/RHSA-2023:0978 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 72415fc89f5dcb558370bd92e670638fc9add9ad19ba4ee77ef546520c9a9e39 emacs-git-1.8.3.1-24.el7_9.noarch.rpm 2d55f68e1a5fb1da8eb138aca00951f0f028a8f3db6a4427488b57f1c043891e emacs-git-el-1.8.3.1-24.el7_9.noarch.rpm d977ef2c9e09f15898d44de8446c4e0984f357c637fa6b2194f05cf87e8abc29 git-1.8.3.1-24.el7_9.x86_64.rpm 48db0a9dafc6ecf4c0b955075d04ff198a44fa5b1bdea37a0f03af3d9d75e1a6 git-all-1.8.3.1-24.el7_9.noarch.rpm 3e669a493af1a126cce0a77eecae0864765c9b701b5640962ecfa5a8ec1afc30 git-bzr-1.8.3.1-24.el7_9.noarch.rpm a0b6efe5d9993351a08c5873bc1be89455d96a5535d9bf69e24384ab21850577 git-cvs-1.8.3.1-24.el7_9.noarch.rpm 4a1eda7aca52060e944393a7b40798a1e90bbd8b4ffcf3bdfe5779ccbe2acc43 git-daemon-1.8.3.1-24.el7_9.x86_64.rpm 2f40644349b7b023a5ac1b6045dc14e19a4d5af38ffd90e8907d4b98929b12b2 git-email-1.8.3.1-24.el7_9.noarch.rpm eace35203de4fbc64ea081a27197877a56615d25b23b30e79f559209ff736310 git-gnome-keyring-1.8.3.1-24.el7_9.x86_64.rpm 6a1b6459f1f724a4030deb520745ead7657fcaae71a35ba2905022d5da341997 git-gui-1.8.3.1-24.el7_9.noarch.rpm 7f8cb3fbedf15a4146ccc43a641071e7f99fbde04c72526476d5cd90545e4644 git-hg-1.8.3.1-24.el7_9.noarch.rpm 37146ed7255163cbdf3bb94a0f5e8ea9cb46eeddd0d269546fb213017f212548 git-instaweb-1.8.3.1-24.el7_9.noarch.rpm b649840984828bb702a86f59b74053d9fb62a7d9512eed421f9ac6fd2c5e648a gitk-1.8.3.1-24.el7_9.noarch.rpm 4f181bcb90816497b5e18006556c8e9c5e26bb5a1da4f5be2acce0472c81866d git-p4-1.8.3.1-24.el7_9.noarch.rpm 37036b6e228127d501401f8546d504c70f6e51fcc1271a33342effbc6d6a62cd git-svn-1.8.3.1-24.el7_9.x86_64.rpm 84b71cd28250d68d8dd0c9a9da4983782f0ef2c5888c5734b7d12841ff61313b gitweb-1.8.3.1-24.el7_9.noarch.rpm 8e6103f5bc92eabbe008d9d10cd7ea86a1fd82eed882657037c36f9c0dd9ef59 perl-Git-1.8.3.1-24.el7_9.noarch.rpm d666c7aa2c9af7b68e1d9bb3646d95b078ea804f6833a701a44fd99fac4c9ae2 perl-Git-SVN-1.8.3.1-24.el7_9.noarch.rpm Source: 188779028ec3e5d4e43e7a0edf533c75725d9086138c787db9f4792636513939 git-1.8.3.1-24.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 212, Issue 1 ***********************************************

1 0

EL9/udev generates wrong device nodes/symlinks with HPE Smart Array controller
by Simon Matter 02 Mar '23

02 Mar '23

Hi, I see some strange and dangerous things happening on a HPE server with HPE Smart Array controller where EL9 ends up with wrong device nodes/symlinks to the attached disks/raid volumes: (I didn't touch anything here but at 08:09 some symlinks were changed) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdc lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_01000000 -> ../../sdb lrwxrwxrwx 1 root root 9 Mar 1 08:09 scsi-0HP_LOGICAL_VOLUME_02000000 -> ../../sda lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_03000000 -> ../../sdd lrwxrwxrwx 1 root root 9 Mar 1 08:09 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdc2 /dev/disk/by-path/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 pci-0000:03:00.0-scsi-0:1:0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 Mar 1 07:57 pci-0000:03:00.0-scsi-0:1:0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Mar 1 07:57 pci-0000:03:00.0-scsi-0:1:0:0-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 9 Mar 1 07:57 pci-0000:03:00.0-scsi-0:1:0:1 -> ../../sdb lrwxrwxrwx 1 root root 9 Mar 1 08:09 pci-0000:03:00.0-scsi-0:1:0:2 -> ../../sda lrwxrwxrwx 1 root root 9 Mar 1 07:57 pci-0000:03:00.0-scsi-0:1:0:3 -> ../../sdd After rebooting, the things are different but also wrong: (here nothing has changed after boot but symlinks are already wrong) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdb lrwxrwxrwx 1 root root 10 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_00000000-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_00000000-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 9 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_01000000 -> ../../sda lrwxrwxrwx 1 root root 9 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_02000000 -> ../../sdd lrwxrwxrwx 1 root root 9 Mar 1 10:56 scsi-0HP_LOGICAL_VOLUME_03000000 -> ../../sdc lrwxrwxrwx 1 root root 9 Mar 1 10:56 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda lrwxrwxrwx 1 root root 10 Mar 1 10:56 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Mar 1 10:56 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2 /dev/disk/by-path/: lrwxrwxrwx 1 root root 9 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 9 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:1 -> ../../sda lrwxrwxrwx 1 root root 9 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:2 -> ../../sdd lrwxrwxrwx 1 root root 9 Mar 1 10:56 pci-0000:03:00.0-scsi-0:1:0:3 -> ../../sdc Note that two things are strange: 1) the /dev/sd* nodes are in a random order after every restart. # lsscsi [1:0:0:0] storage HP P410i 6.64 - [1:1:0:0] disk HP LOGICAL VOLUME 6.64 /dev/sdb [1:1:0:1] disk HP LOGICAL VOLUME 6.64 /dev/sda [1:1:0:2] disk HP LOGICAL VOLUME 6.64 /dev/sdd [1:1:0:3] disk HP LOGICAL VOLUME 6.64 /dev/sdc 2) some symlinks created by udev are just wrong and therefore very dangerous to use: scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1 scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2 While 1 may be expected(???) I think 2 should really not happen. I've tried to find out where things go wrong but the whole udev stuff started to hurt my brain :) I'm quite sure HPE Smart Array based servers are quite common so my big question is: do others see that same? While it's possible to live with this mess I'd really like to fix it somehow. Thanks, Simon

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2023