July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1181705] VUL-0: CVE-2020-15690: nim: Standard library asyncftpclient lacks a check for newline character
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1181705 David Anes <david.anes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.anes(a)suse.com Assignee|anicka(a)suse.com |david.anes(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201385] AUDIT-0: postfix: review of permissions-file-setuid-bit: /usr/sbin/postlog (02755)
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201385 http://bugzilla.opensuse.org/show_bug.cgi?id=1201385#c9 --- Comment #9 from Christian Wittmer <chris(a)computersalat.de> --- (In reply to Matthias Gerstner from comment #8) > (In reply to chris(a)computersalat.de from comment #7) > > Will there also be an update of permissions pkg for Leap 15.3 and 15.4 ? > > If you need it, yes. Will it be the same postfix version? Yes, will be needed for postfix version 3.7.x so I can update pkg in server:mail -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193336] New: "systemd-udev-settle.service is deprecated. Please fix multipathd.service not to pull it in."
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193336 Bug ID: 1193336 Summary: "systemd-udev-settle.service is deprecated. Please fix multipathd.service not to pull it in." Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Warning during boot: > udevadm[2615]: systemd-udev-settle.service is deprecated. Please fix multipathd.service not to pull it in. Latest upstream multipath-tools was redesigned such that the dependency on systemd-udev-settle can indeed be dropped. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1187020] multipath-tools: unconditionally loads modules
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1187020 https://bugzilla.suse.com/show_bug.cgi?id=1187020#c1 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Martin Wilck <martin.wilck(a)suse.com> --- No, we can't do that. I have put quite a bit of thought into this for SLE15-SP4. In particular the SCSI device handlers modules _must_ be loaded before any probing of SCSI devices starts. The only viable alternative to modules-load.d would be a softdep on scsi_mod, but that doesn't work on TW because scsi_mod is built-in (sic). I don't think it hurts much because these modules are very small. We could discuss reducing the set, only scsi_dh_alua (and perhaps scsi_dh_rdac) should be required these days. The situation is somewhat different for the dm-multipath module itself. In principle, we *could* load it on demand. But we can't do it only from multipathd.service. "multipath" is run from udev rules during early boot. The tools themselves would need to gain the ability to load the module if it isn't present. Currently that's not supported. So for now, we need to keep the modules-load.d file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193059] New: suse-module-tools: split modprobe.conf defaults into multiple files
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193059 Bug ID: 1193059 Summary: suse-module-tools: split modprobe.conf defaults into multiple files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We have moved all default modprobe.conf settings to /usr/lib/modprobe.d now. This makes it easier for users to override distro defaults by copying .conf files to /etc/modprobe.d and editing them. This is still suboptimal though, because we collect all settings in two big files, 00-system.conf and 50-blacklist.conf. A user who wants to override a single setting has to override the entire file, meaning that she won't see future updates. It would be much better and much more to the modprobe.d spirit to split the modprobe.conf files into multiple small files, each for just one module or for a small collection of closely related modules. This way, users could easily override the settings for just one module. It's intended that users should be able to to this, as we are shipping quite a few modules that are blacklisted by default and would be utterly useless if un-blacklisting them wouldn't be accepted practice. With this change, a default modprobe.d directory would look like this: # ls -l /usr/lib/modprobe.d/ total 204 -rw-r--r-- 1 root root 1298 Nov 22 23:36 10-unsupported-modules.conf -rw-r--r-- 1 root root 21 Nov 22 23:36 40-alias-autofs.conf -rw-r--r-- 1 root root 15 Nov 22 23:36 40-alias-nfs.conf -rw-r--r-- 1 root root 81 Nov 22 23:36 40-alias-paride.conf -rw-r--r-- 1 root root 34 Nov 22 23:36 40-alias-parport.conf -rw-r--r-- 1 root root 75 Nov 22 23:36 40-alias-qemu-acpiphp.conf -rw-r--r-- 1 root root 83 Nov 22 23:36 40-apm.conf -rw-r--r-- 1 root root 728 Nov 22 23:36 40-bttv_skip_it.conf -rw-r--r-- 1 root root 134 Nov 22 23:36 40-cifs.conf -rw-r--r-- 1 root root 63 Nov 22 23:36 40-rtc.conf -rw-r--r-- 1 root root 87 Nov 22 23:36 40-sonypi.conf -rw-r--r-- 1 root root 32 Nov 22 23:36 40-toshiba.conf -rw-r--r-- 1 root root 424 Nov 22 23:36 50-blacklist-acpi_power_meter.conf -rw-r--r-- 1 root root 41 Nov 22 23:36 50-blacklist-bfusb.conf -rw-r--r-- 1 root root 78 Nov 22 23:36 50-blacklist-dpt_i2o.conf -rw-r--r-- 1 root root 175 Nov 22 23:36 50-blacklist-evbug.conf -rw-r--r-- 1 root root 1477 Nov 22 23:36 50-blacklist-fb.conf -rw-r--r-- 1 root root 131 Nov 22 23:36 50-blacklist-mtd.conf -rw-r--r-- 1 root root 230 Nov 22 23:36 50-blacklist-pata_acpi.conf -rw-r--r-- 1 root root 87 Nov 22 23:36 50-blacklist-snd_bt87x.conf -rw-r--r-- 1 root root 81 Nov 22 23:36 50-blacklist-usbcore.conf -rw-r--r-- 1 root root 183 Nov 22 23:36 50-blacklist-xircom.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-adfs.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-affs.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-befs.conf -rw-r--r-- 1 root root 415 Nov 22 23:38 60-blacklist_fs-bfs.conf -rw-r--r-- 1 root root 433 Nov 22 23:38 60-blacklist_fs-cramfs.conf -rw-r--r-- 1 root root 415 Nov 22 23:38 60-blacklist_fs-efs.conf -rw-r--r-- 1 root root 427 Nov 22 23:38 60-blacklist_fs-erofs.conf -rw-r--r-- 1 root root 427 Nov 22 23:38 60-blacklist_fs-exofs.conf -rw-r--r-- 1 root root 445 Nov 22 23:38 60-blacklist_fs-freevxfs.conf -rw-r--r-- 1 root root 415 Nov 22 23:38 60-blacklist_fs-hfs.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-hpfs.conf -rw-r--r-- 1 root root 415 Nov 22 23:38 60-blacklist_fs-jfs.conf -rw-r--r-- 1 root root 427 Nov 22 23:38 60-blacklist_fs-minix.conf -rw-r--r-- 1 root root 433 Nov 22 23:38 60-blacklist_fs-nilfs2.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-ntfs.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-omfs.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-qnx4.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-qnx6.conf -rw-r--r-- 1 root root 421 Nov 22 23:38 60-blacklist_fs-sysv.conf -rw-r--r-- 1 root root 415 Nov 22 23:38 60-blacklist_fs-ufs.conf -rw-r--r-- 1 root root 69 Nov 22 23:36 70-softdep-ata_piix.conf -rw-r--r-- 1 root root 102 Nov 22 23:36 70-softdep-csiostor.conf -rw-r--r-- 1 root root 54 Nov 22 23:36 70-softdep-dm_crypt.conf -rw-r--r-- 1 root root 163 Nov 22 23:36 70-softdep-ehci_hcd.conf -rw-r--r-- 1 root root 170 Nov 22 23:36 70-softdep-usb_storage.conf -rw-r--r-- 1 root root 117 Nov 22 23:36 80-options-ch.conf -rw-r--r-- 1 root root 306 Oct 15 14:09 README -rw-r--r-- 1 root root 158 Oct 11 17:05 firewalld-sysctls.conf -rw-r--r-- 1 root root 773 Oct 15 14:09 systemd.conf Un-blacklisting a single entry is now as easy as doing e.g. "ln -s /dev/null /etc/modprobe.d/50-blacklist-snd_bt87x.conf". This is the same technique used e.g. by udev or systemd to override system defaults. The change has one disadvantage though - kmod operations will be slower, because reading many small files takes more time than reading one big file. The time for reading all conf files (standard TW installation, x86_64, SATA SSD) is: Before: with cold page cache: 34.6 ms, hot cache: 11.8 ms After: with cold page cache: 41.3 ms, hot cache: 14.7 ms The entire modprobe operation typically takes 200-300 ms on the same system. Note that some modprobe.conf files are already shipped in "split" fashion, in particular the file system blacklist files like 60-blacklist_fs-hpfs.conf, and some modprobe.d files that are shipped in other packages. With 200 modules loaded after boot and no paralellism, this could slow down system boot by up to 500-1000 ms. The question is whether this would be an acceptable price to pay for better customizability and cleaner configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1193334] New: multipathd: double free in remove_map()
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193334 Bug ID: 1193334 Summary: multipathd: double free in remove_map() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Original bug report from Lixiaokeng ("libmultipath: clear removed path from mpp") upstream: multipathd[3525635]: ==3525635==ERROR: AddressSanitizer: heap-use-after-free on address 0xffffa4902fc0 at pc 0xffffac7d5b88 bp 0xffffa948dac0 sp 0xffffa948dae0 multipathd[3525635]: READ of size 8 at 0xffffa4902fc0 thread T7 multipathd[3525635]: #0 0xffffac7d5b87 in free_multipath (/usr/lib64/libmultipath.so.0+0x4bb87) multipathd[3525635]: #1 0xaaaad6cf7057 (/usr/sbin/multipathd+0x17057) multipathd[3525635]: #2 0xaaaad6cf78eb (/usr/sbin/multipathd+0x178eb) multipathd[3525635]: #3 0xaaaad6cff4df (/usr/sbin/multipathd+0x1f4df) multipathd[3525635]: #4 0xaaaad6cfffe7 (/usr/sbin/multipathd+0x1ffe7) multipathd[3525635]: #5 0xffffac807be3 in uevent_dispatch (/usr/lib64/libmultipath.so.0+0x7dbe3) multipathd[3525635]: #6 0xaaaad6cf563f (/usr/sbin/multipathd+0x1563f) multipathd[3525635]: #7 0xffffac6877af (/usr/lib64/libpthread.so.0+0x87af) multipathd[3525635]: #8 0xffffac44118b (/usr/lib64/libc.so.6+0xd518b) multipathd[3525635]: 0xffffa4902fc0 is located 1344 bytes inside of 1440-byte region [0xffffa4902a80,0xffffa4903020) multipathd[3525635]: freed by thread T7 here: multipathd[3525635]: #0 0xffffac97d703 in free (/usr/lib64/libasan.so.4+0xd0703) multipathd[3525635]: #1 0xffffac824827 in orphan_paths (/usr/lib64/libmultipath.so.0+0x9a827) multipathd[3525635]: #2 0xffffac824a43 in remove_map (/usr/lib64/libmultipath.so.0+0x9aa43) multipathd[3525635]: #3 0xaaaad6cf7057 (/usr/sbin/multipathd+0x17057) multipathd[3525635]: #4 0xaaaad6cf78eb (/usr/sbin/multipathd+0x178eb) multipathd[3525635]: #5 0xaaaad6cff4df (/usr/sbin/multipathd+0x1f4df) multipathd[3525635]: #6 0xaaaad6cfffe7 (/usr/sbin/multipathd+0x1ffe7) multipathd[3525635]: #7 0xffffac807be3 in uevent_dispatch (/usr/lib64/libmultipath.so.0+0x7dbe3) multipathd[3525635]: #8 0xaaaad6cf563f (/usr/sbin/multipathd+0x1563f) multipathd[3525635]: #9 0xffffac6877af (/usr/lib64/libpthread.so.0+0x87af) multipathd[3525635]: #10 0xffffac44118b (/usr/lib64/libc.so.6+0xd518b) When mpp only has one path and log out the path, there is an asan error. In remove_mpp, the pp is freed firstly in orphan_path but is accessed, changed in free_multipath later. Before free_path(pp), the pp should be cleared from pp->mpp. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193338] New: multipathd won't start when stopped during reconfigure
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193338 Bug ID: 1193338 Summary: multipathd won't start when stopped during reconfigure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After sending "RELOADING=1" to systemd, a service must send "READY=1" before "STOPPING=1". Otherwise systemd will be confused and will not regard the service as stopped. Subsequent attempts to start multipathd via socket activation fail until systemd times out the reload operation. The problem can be reproduced by running "multipathd shutdown" quickly after "multipathd reconfigure". Solved in latest upstream multipath-tools. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193342] New: Various coverity defects in multipath-tools
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193342 Bug ID: 1193342 Summary: Various coverity defects in multipath-tools Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Coverity finds a number of defects in multipath-tools. A recent upstream patch series fixes all of them. df9ccd5 libmultipath (coverity): check return values in dm_get_multipath() 2e61b8f libmultipath (coverity): Revert "setup_map: wait for pending path checkers to finish" f455285 libmultipath (coverity): avoid sleeping in dm_mapname() d770ae2 multipathd (coverity): daemonize(): use dup2 b0f6df5 kpartx: find_unused_loop_device(): add newlines 7c6714e kpartx: use opened loop device immediately 1ffd7c9 kpartx: open /dev/loop-control only once 8c71adc multipathd (coverity): simplify set_oom_adj() 75d580a libmultipath (coverity): set umask before mkstemp 8f6c9fc multipath: remove pointless code from getopt processing f6e71e8 libmultipath (coverity): silence unchecked return value warning c9c7db3 multipath, multipathd: exit if bindings file is broken ed7dc96 libmultipath (coverity): fix tainted values in alua_rtpg.c 5ed05b1 libmultipath: use strbuf in parse_vpd_pg83() 216845c multipath-tools: add tests for broken VPD page 83 d331b8a libmultipath (coverity): improve input checking in parse_vpd_pg83 df63773 libmultipath: strbuf: add __get_strbuf_buf() 544a75d multipathd (coverity): terminate uxlsnr when polls allocation fails bcb771e multipathd (coverity): check atexit() return value -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193759] New: bfq scheduler set on loop devices
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193759 Bug ID: 1193759 Summary: bfq scheduler set on loop devices Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- while chasing something else I noticed that on my tumbleweed system, all loop back block devices are having a "bfq" scheduler set. $ grep . /sys/block/loop1/queue/scheduler /sys/block/loop1/queue/scheduler:mq-deadline kyber [bfq] none does that make sense? why? I was expecting something like "none" instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1182227] combustion [# combustion: network] does not work
by bugzilla_noreply＠suse.com 14 Jul '22

14 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1182227 https://bugzilla.suse.com/show_bug.cgi?id=1182227#c50 --- Comment #50 from Markus Zimmermann <markus.zimmermann(a)symflower.com> --- One additional observation: shouldn't NetworkManager change the connections with the command? Because there is only the standard "Wired Connection" afterwards. In comparison when i do that: ``` cat <<EOT >> /etc/NetworkManager/system-connections/enp1s0.nmconnection [connection] id=enp1s0 type=ethernet interface-name=enp1s0 [ethernet] [ipv4] address1=192.168.122.10/24,192.168.122.1 method=manual EOT chmod 0700 /etc/NetworkManager/system-connections chmod 0600 /etc/NetworkManager/system-connections/enp1s0.nmconnection ``` I still do not have a static IP, but now i have two connections at least showing up: ``` # nmcli connection show NAME UUID TYPE DEVICE Wired Connection 2e1e20dd-217c-4891-8a97-ce6a88659773 ethernet enp1s0 enp1s0 360d1330-11cf-3a91-ae05-590058fc3e82 ethernet -- ``` Whatever it is, this bug says to me that MicroOS cannot do a static IP address automatic setup via Combustion nor Ignation. I tried both. Same problem. I do not know what else to do since there is no cloud-init installed (AFAIK) for the KVM version and i do not know how to forward kernel arguments when i am using no location argument with "virt-install", only the .qcow2 as base. -- You are receiving this mail because: You are on the CC list for the bug.

1 0