Discuss February 2018

discuss@lists.centos.org

96 participants
71 discussions

Meltdown and Spectre
by isdtor 12 Feb '18

12 Feb '18

Does anyone know if Red Hat are working on backporting improved mitigation techniques and features from newer, 4.14.14+ kernels? $ grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI /sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable: Minimal generic ASM retpoline $

2 1

CentOS 7 Cloud 16.0.4 Nova Security Update
by Henry Spanka 10 Feb '18

10 Feb '18

Hello, A security issue has been found in Nova 16.0.3 and a fix has been released in December, however I haven’t seen Nova 16.0.4 in the Cloud repositories yet. Is someone working on updating the nova packages? The issue allows users to consume all resources on a host which leads to a denial of service. See: https://docs.openstack.org/releasenotes/nova/pike.html <https://docs.openstack.org/releasenotes/nova/pike.html> Vulnerability ID: OSSA-2017-006 ----------------------------------------------------------------------------------------- Mit freundlichen Grüßen / With best regards Henry Spanka — myVirtualserver — Development Team GPG: 8BA3 14FE 3973 9E17 1D9E ADAE CEAB DAB5 5B47 0BC8

1 0

Issues with NVidia video driver and CentOS
by Felipe Westfields 09 Feb '18

09 Feb '18

I'm having issues with a quad video card on CentOS. We have several systems on CentOS 6.8 and CentOS 6.9. The installed hardware is: Video card - Nvidia NVS quadro 440 PC - Dell OptiPlex 9020 Whenever you update the kernel, it kills the graphical interface. The system appears to lock up and freeze during a reboot, but you can still get into it with SSH, or, if you're at the console, control-alt-F2 gets you to a command prompt. If you exclude the kernel update when applying yum update, it is usually fine. If the kernel update is applied, and you roll back the update, that sometimes gets you back into the graphical console, but more likely than not, it won't. Not sure where to go with this. Any suggestions? FW

6 12

Adjust type of rw in submit_bio from int to unsigned long
by wuzhouhui 09 Feb '18

09 Feb '18

Hi, I am a developer who worked on CentOS. Recently I am working on porting one of my block drivers from CentOS 6.x to CentOS 7.x. In newest kernel (kernel-3.10.0-693.17.1.el7) I found there is an issue in submit_bio()'s first argument: void submit_bio(int rw, struct bio *bio) The type of bi_rw of struct bio is unsigned long, and the number of enum rq_flags_bits also exceeds 32, so we should better using unsigned long for rw in submit_bio(), like: void submit_bio(unsigned long rw, struct bio *bio)

1 1

OT: configuring xming to know putty's not in a std. location
by m.roth＠5-cent.us 08 Feb '18

08 Feb '18

Is there some way to do this? I've got the current putty (actually, putty-cac), pageant, and plink in my user's Downlods directory - neither he nor I have admin authority on his laptop, and Desktop support's teleworking today - but I can't seem to find a way to configure xming to look there for putty. Or is it start putty, *then* start xming? mark

5 5

OT - pushing database updates to web browser
by Gary Stainburn 07 Feb '18

07 Feb '18

This is O/T apart from the fact that the server is Centos running Apache / Postgresql. I want to develop a real time (ish) dashboard type web page showring extracts of the contents of a table. I would like any changes that occur to be pushed to the web clients rather than have the clients poll the database. Based on the fact that I have not managed to come up with a successful Google search phrase I think this may not be possible, but just in case I thought I'd ask here. If it's not possible, can anyone suggest the most efficient / responsive polling techniques?

3 3

/dev/md1 => 93% Used. Warning. Disk Filling up. - what would be safe to delete in /boot ?
by Alexander Farber 07 Feb '18

07 Feb '18

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc. remotely... and at the same time I am not proficient with grub or whatever my provider has configured my dedicated hosts to use... # ls -al /boot total 427877 dr-xr-xr-x. 6 root root 6144 28. Jan 10:33 . dr-xr-xr-x 18 root root 4096 7. Feb 03:34 .. -rw-r--r-- 1 root root 140899 5. Dez 01:04 config-3.10.0-693.11.1.el7.x86_64 -rw-r--r-- 1 root root 140915 4. Jan 02:19 config-3.10.0-693.11.6.el7.x86_64 -rw-r--r-- 1 root root 140915 25. Jan 21:26 config-3.10.0-693.17.1.el7.x86_64 -rw-r--r-- 1 root root 140898 13. Sep 00:38 config-3.10.0-693.2.2.el7.x86_64 -rw-r--r-- 1 root root 140898 20. Okt 22:56 config-3.10.0-693.5.2.el7.x86_64 drwxr-xr-x 3 root root 1024 15. Sep 09:43 efi drwxr-xr-x. 2 root root 1024 11. Apr 2016 grub drwx------. 5 root root 1024 28. Jan 10:31 grub2 -rw-r--r--. 1 root root 40142116 15. Dez 2015 initramfs-0-rescue-34946d7b5edb0946bfb52c0f6cae67af.img -rw------- 1 root root 50402914 6. Dez 09:23 initramfs-3.10.0-693.11.1.el7.x86_64.img -rw------- 1 root root 18149718 6. Dez 09:24 initramfs-3.10.0-693.11.1.el7.x86_64kdump.img -rw------- 1 root root 50405879 5. Jan 09:02 initramfs-3.10.0-693.11.6.el7.x86_64.img -rw------- 1 root root 18150336 5. Jan 09:04 initramfs-3.10.0-693.11.6.el7.x86_64kdump.img -rw------- 1 root root 50402830 28. Jan 10:31 initramfs-3.10.0-693.17.1.el7.x86_64.img -rw------- 1 root root 18147918 28. Jan 10:33 initramfs-3.10.0-693.17.1.el7.x86_64kdump.img -rw------- 1 root root 50341850 15. Sep 09:45 initramfs-3.10.0-693.2.2.el7.x86_64.img -rw------- 1 root root 18147818 22. Okt 10:07 initramfs-3.10.0-693.2.2.el7.x86_64kdump.img -rw------- 1 root root 50393743 24. Okt 09:39 initramfs-3.10.0-693.5.2.el7.x86_64.img -rw------- 1 root root 18146720 24. Okt 09:40 initramfs-3.10.0-693.5.2.el7.x86_64kdump.img -rw-r--r--. 1 root root 611928 15. Sep 09:45 initrd-plymouth.img drwx------ 2 root root 12288 25. Mai 2016 lost+found -rw-r--r-- 1 root root 293093 5. Dez 01:07 symvers-3.10.0-693.11.1.el7.x86_64.gz -rw-r--r-- 1 root root 293110 4. Jan 02:21 symvers-3.10.0-693.11.6.el7.x86_64.gz -rw-r--r-- 1 root root 293109 25. Jan 21:28 symvers-3.10.0-693.17.1.el7.x86_64.gz -rw-r--r-- 1 root root 293064 13. Sep 00:40 symvers-3.10.0-693.2.2.el7.x86_64.gz -rw-r--r-- 1 root root 293084 20. Okt 22:59 symvers-3.10.0-693.5.2.el7.x86_64.gz -rw------- 1 root root 3228852 5. Dez 01:04 System.map-3.10.0-693.11.1.el7.x86_64 -rw------- 1 root root 3232490 4. Jan 02:19 System.map-3.10.0-693.11.6.el7.x86_64 -rw------- 1 root root 3232454 25. Jan 21:26 System.map-3.10.0-693.17.1.el7.x86_64 -rw------- 1 root root 3228852 13. Sep 00:38 System.map-3.10.0-693.2.2.el7.x86_64 -rw------- 1 root root 3228852 20. Okt 22:56 System.map-3.10.0-693.5.2.el7.x86_64 -rwxr-xr-x. 1 root root 5156528 15. Dez 2015 vmlinuz-0-rescue-34946d7b5edb0946bfb52c0f6cae67af -rwxr-xr-x 1 root root 5877504 5. Dez 01:05 vmlinuz-3.10.0-693.11.1.el7.x86_64 -rw-r--r-- 1 root root 171 5. Dez 01:05 .vmlinuz-3.10.0-693.11.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 5889728 4. Jan 02:19 vmlinuz-3.10.0-693.11.6.el7.x86_64 -rw-r--r-- 1 root root 171 4. Jan 02:19 .vmlinuz-3.10.0-693.11.6.el7.x86_64.hmac -rwxr-xr-x 1 root root 5890720 25. Jan 21:26 vmlinuz-3.10.0-693.17.1.el7.x86_64 -rw-r--r-- 1 root root 171 25. Jan 21:26 .vmlinuz-3.10.0-693.17.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 5878848 13. Sep 00:38 vmlinuz-3.10.0-693.2.2.el7.x86_64 -rw-r--r-- 1 root root 170 13. Sep 00:38 .vmlinuz-3.10.0-693.2.2.el7.x86_64.hmac -rwxr-xr-x 1 root root 5878368 20. Okt 22:56 vmlinuz-3.10.0-693.5.2.el7.x86_64 -rw-r--r-- 1 root root 170 20. Okt 22:56 .vmlinuz-3.10.0-693.5.2.el7.x86_64.hmac # cat /etc/grub2.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### set pager=1 if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } terminal_output console if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/01_users ### if [ -f ${prefix}/user.cfg ]; then source ${prefix}/user.cfg if [ -n "${GRUB2_PASSWORD}" ]; then set superusers="root" export superusers password_pbkdf2 root ${GRUB2_PASSWORD} fi fi ### END /etc/grub.d/01_users ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'CentOS Linux (3.10.0-693.17.1.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.17.1.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.17.1.el7.x86_64.img } menuentry 'CentOS Linux (3.10.0-693.11.6.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.11.6.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.11.6.el7.x86_64.img } menuentry 'CentOS Linux (3.10.0-693.11.1.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.11.1.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.11.1.el7.x86_64.img } menuentry 'CentOS Linux (3.10.0-693.5.2.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.5.2.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.5.2.el7.x86_64.img } menuentry 'CentOS Linux (3.10.0-693.2.2.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.2.2.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.2.2.el7.x86_64.img } menuentry 'CentOS Linux (0-rescue-34946d7b5edb0946bfb52c0f6cae67af) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-34946d7b5edb0946bfb52c0f6cae67af-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b' { load_video insmod gzio insmod part_msdos insmod part_msdos insmod diskfilter insmod mdraid1x insmod ext2 set root='mduuid/84bbf877f8bd0f7aa0c64064178966b4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-0-rescue-34946d7b5edb0946bfb52c0f6cae67af root=UUID=2a4bc862-eb7a-46b1-8979-d19c873dca3b ro nomodeset rd.auto=1 crashkernel=auto initrd16 /initramfs-0-rescue-34946d7b5edb0946bfb52c0f6cae67af.img } if [ "x$default" = 'CentOS Linux (3.10.0-327.13.1.el7.x86_64) 7 (Core)' ]; then default='Advanced options for CentOS Linux>CentOS Linux (3.10.0-327.13.1.el7.x86_64) 7 (Core)'; fi; ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_ppc_terminfo ### ### END /etc/grub.d/20_ppc_terminfo ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### Thank you for any hints Alex

2 2

Allowing non-root users to reboot a workstation
by Felipe Westfields 06 Feb '18

06 Feb '18

I would like to be able to allow regular users that don't have admin privileges to be able to reboot their workstation. (they're software developers so rebooting their workstation doesn't affect anybody else) I tried changing the ownership of /sbin/reboot and /sbin/shutdown to root:users and permissions to 550, but that didn't work - it's still asking for root privileges. Possibly the problem might be that there's centralized LDAP authentication, not local, so the changes I made only apply to local accounts? Any suggestions? FW

7 7

Slightly OT : newsletters, mail formatting and netiquette
by Nicolas Kovacs 06 Feb '18

06 Feb '18

Hi, This question is not exactly CentOS-related strictly speaking, but here goes. I'm running a few newsletter servers for myself and a handful of clients on public CentOS servers with PHPList. For the last twenty years or so I've followed the basic rule that mails should have no formatting whatsoever, only simple text. And now I wonder if that basic rule of netiquette also applies to newsletters. I'm a subscriber to a series of tech-related newsletters, and I couldn't help but notice that they all seem to be HTML-formatted, even those from respectable hardcore geek groups. So my somewhat naive question: is HTML formatting acceptable in newsletters? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

6 6

Re: [CentOS] CentOS Digest, Vol 157, Issue 4
by Stephen Davies 06 Feb '18

06 Feb '18

On 04/02/18 22:30, centos-request(a)centos.org wrote: ---------------- > > Message: 1 > Date: Sat, 3 Feb 2018 16:57:19 -0800 > From: Akemi Yagi <amyagi(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Update to 3.10.0-693.17.1 breaks ath5k > Message-ID: > <CABA31DoCu6Yf7_nkN6s0Zz=THvrpqAcFfj2=2oTmscTpEPD3XA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Fri, Feb 2, 2018 at 10:57 PM, Stephen Davies <sdavies(a)sdc.com.au> wrote: >> Where can I find a suitable module or even source code to build here? >> >> (Centos 7) > > ELRepo used to provide the kmod-ath5k package. However, the module > does not compile under EL7.4 due to the change in the wireless stack. > If your device needs ath5k, give ELRepo's kernel-lt a try. The module > is enabled in this kernel. > > Akemi > > I have worked around this issue by changing the default boot image to the previous release. I realise that this leaves the Intel issue but I can live with that and without future kernel updates. Hopefully somebody will fix the module before I die. Cheers, Stephen

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss February 2018