July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1186027] New: VUL-1: CVE-2021-32917,CVE-2021-32918,CVE-2021-32919,CVE-2021-32920,CVE-2021-32921: Prosody XMPP server advisory 2021-05-12 (multiple vulnerabilities)
by bugzilla_noreply＠suse.com 05 Feb '23

05 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186027 Bug ID: 1186027 Summary: VUL-1: CVE-2021-32917,CVE-2021-32918,CVE-2021-32919,CVE-2021- 32920,CVE-2021-32921: Prosody XMPP server advisory 2021-05-12 (multiple vulnerabilities) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/284222/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: mvetter(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- Prosody security advisory 2021-05-12 ==================================== Project : Prosody XMPP server URL : https://prosody.im/ Date : 2021-05-12 This advisory details 5 new security vulnerabilities discovered in the Prosody.im XMPP server software. All issues are fixed in the 0.11.9 release default configuration. **References** - Release announcement: https://blog.prosody.im/prosody-0.11.9-released/ - Advisory (HTML): https://prosody.im/security/advisory_20210512/ - Advisory (text): https://prosody.im/security/advisory_20210512.txt 1/5: DoS via insufficient memory consumption controls ----------------------------------------------------- CVE : CVE-2021-32918 CVSS : 7.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C) CWEs : CWE-400 Affected versions : All versions prior to 0.11.9 Fixed versions : 0.11.9, 0.11 nightly build 130, trunk nightly build 1434 **Description** It was discovered that default settings leave Prosody susceptible to remote unauthenticated denial-of-service (DoS) attacks via memory exhaustion when running under Lua 5.2 or Lua 5.3. Lua 5.2 is the default and recommended Lua version for Prosody 0.11.x series. **Affected configurations** The default configuration is susceptible to this issue. Configurations with stricter settings for stanza size limits, rate limits and garbage collection parameters are at decreased risk from this attack. For more details please review the 'Mitigation' section for recommended values. **Mitigation** Mitigation is possible through configuration changes (on 0.11.7+). All the configuration changes described in this section are applied by default in Prosody 0.11.9. 1) Enable more aggressive garbage collection On Lua 5.2 and 5.3, the garbage collector does not free unused memory fast enough by default. This allowed Prosody's memory usage to grow excessively during certain traffic patterns. It is recommended to set a garbage collection speed of at least 500 in the global section of your configuration file: ``` gc = { speed = 500; } ``` Be aware that this setting may increase CPU usage if the other mitigations in this section are not applied. 2) Enable stricter stanza size limits By default Prosody ships with extremely permissive stanza size limits (up to 10MB). This value was introduced as a way to place a limit on memory usage without affecting legitimate use of the server. However testing demonstrates that the default limit is too high for most deployments. Our recommendation (and the default in 0.11.9) is to adopt the same default size limits that are already enforced by ejabberd, one of the other major XMPP servers on the network. To enable the new limits explicitly, add to the global section of your configuration file the following options: c2s_stanza_size_limit = 256 * 1024 s2s_stanza_size_limit = 512 * 1024 Be aware that reducing limits has the potential to introduce interoperability issues with deployments that do not enforce the same size limits. For example, remote contacts with large avatars. 3) Enable rate limits By default Prosody does not enable any rate limits. However we recommend enabling them for all production and public deployments to ensure fair consumption of resources across all connections. First, ensure that mod_limits is enabled by adding "limits" to your global modules_enabled configuration option: ``` modules_enabled = { ... "limits"; ... } ``` Next, configure the limits: ``` limits = { c2s = { rate = "10kb/s"; }; s2sin = { rate = "30kb/s"; } } ``` **Advice** All public deployments should upgrade to 0.11.9 or apply the above configuration changes. Deployments using nightly builds should upgrade to the latest available builds. **Credits** Many thanks to Travis Burtrum (moparisthebest) for discovering and reporting this issue, and providing a test case. **Commits** - https://hg.prosody.im/trunk/rev/db8e41eb6eff - https://hg.prosody.im/trunk/rev/b0d8920ed5e5 - https://hg.prosody.im/trunk/rev/929de6ade6b6 - https://hg.prosody.im/trunk/rev/63fd4c8465fb - https://hg.prosody.im/trunk/rev/1937b3c3efb5 - https://hg.prosody.im/trunk/rev/3413fea9e6db ---------------------------------------------------------------------------- 2/5: DoS via repeated TLS renegotiation causing excessive CPU consumption ---------------------------------------------------------------------------- CVE : CVE-2021-32920 CVSS : 5.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:H/RL:O/RC:C) CWEs : CWE-400 Affected versions : All versions prior to 0.11.9 Fixed versions : 0.11.9, 0.11 nightly build 130, trunk nightly build 1434 **Description** It was discovered that Prosody does not disable SSL/TLS renegotiation, even though this is not used in XMPP. A malicious client may flood a connection with renegotiation requests to consume excessive CPU resources on the server. Support for disabling renegotiation depends on OpenSSL 1.1.1+ and LuaSec 0.7+. **Affected configurations** The default configuration is susceptible to this issue. **Temporary mitigation** Ensure you have OpenSSL 1.1.1 or higher and LuaSec 0.7 or higher, and set the following ssl option (or add to your existing one if you have one): ``` ssl = { options = { no_renegotiation = true; } } ``` This configuration is applied by default in 0.11.9. **Advice** All public deployments should upgrade to 0.11.9 or apply the above configuration changes. Deployments using nightly builds should upgrade to the latest available builds. **Credits** This flaw was discovered by Kim Alvefur, a member of the Prosody team. **Commits** - https://hg.prosody.im/trunk/rev/55ef50d6cf65 - https://hg.prosody.im/trunk/rev/5a484bd050a7 - https://hg.prosody.im/trunk/rev/aaf9c6b6d18d ----------------------------------------------------------------------- 3/5: Use of timing-dependent string comparison with sensitive values ----------------------------------------------------------------------- CVE : CVE-2021-32921 CVSS : 4.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:U) CWEs : CWE-1254 Affected versions : All versions prior to 0.11.9 Fixed versions : 0.11.9, 0.11 nightly build 130, trunk nightly build 1434 **Description** It was discovered that Prosody does not use a constant-time algorithm for comparing certain secret strings when running under Lua 5.2 or later. This can potentially be used in a timing attack to reveal the contents of secret strings to an attacker. Lua 5.1 utilizes a technique called "string interning", which protected string comparisons from timing attacks. In Lua 5.2 and later versions, strings over 40 bytes in length are excluded from interning. With Prosody running under Lua 5.2, this makes any secret string over 40 bytes in length vulnerable to potential discovery via timing attacks. Note that if a secret string contains non-ASCII (unicode) characters, it may be longer than 40 bytes when encoded as UTF-8 (Prosody's internal encoding) even if it is fewer than 40 characters long. It should be noted that to successfully perform a timing attack, a significant number of failed attempts must typically be made to "guess" at the contents of the secret string. We are not aware of any attempts to exploit this vulnerability (which would likely be noticeable), and no known proof-of-concept exploit exists. **Affected configurations** This flaw affects the following modules: - mod_auth_internal_plain (disabled by default) mod_auth_internal_plain performs a timing-dependent comparison to the user's password if the user's password is longer than 40 bytes. This may allow an attacker to discover a user's password via a timing attack. We do not generally recommend mod_auth_internal_plain for new deployments, and mod_auth_internal_hashed has been the default for Prosody 0.11.x. - mod_muc (disabled by default) mod_muc supports password-protection of MUCs. The password validity check is performed using a timing-dependent comparison, which may allow an attacker to discover the MUC password via a timing attack if the password is longer than 40 bytes. We do not generally recommend using password-protected MUCs. Instead use affiliations to directly grant access to specific JIDs whenever possible. - mod_auth_internal_hashed (enabled by default but not typically vulnerable) mod_auth_internal_hashed has been updated for safety, but it is not vulnerable in the default configuration of Lua 5.2 as the password hashes it compares do not exceed 40 bytes. - mod_dialback (enabled by default but not typically vulnerable) mod_dialback has been updated for safety, but due to the single-use nature of s2s dialback verification strings a timing attack on this module is not believed to be possible, or to grant an attacker any advantage if it were. **Temporary mitigation** mod_auth_internal_plain: we recommend that people upgrade to mod_auth_internal_hashed due to this and also to benefit from its other security properties. mod_muc: use affiliations to grant access to a MUC instead of passwords. If passwords must be used, ensure they are shorter than 40 bytes. Rate limits can greatly lengthen the amount of time required to successfully complete a timing attack. Enable and configure mod_limits. **Advice** All deployments should upgrade to 0.11.9. Deployments using nightly builds should upgrade to the latest available builds. **Credits** This flaw was discovered by Matthew Wild, a member of the Prosody team. The issue with MUC passwords was also previously identified by Robert Gr��sser. **Commits** - https://hg.prosody.im/trunk/rev/c98aebe601f9 - https://hg.prosody.im/trunk/rev/13b84682518e - https://hg.prosody.im/trunk/rev/6f56170ea986 ------------------------------------------------------------------- 4/5: Use of mod_proxy65 is unrestricted in default configuration ------------------------------------------------------------------- CVE : CVE-2021-32917 CVSS : 5.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:H/RL:O/RC:C) CWEs : CWE-862, CWE-400 Affected versions : All versions prior to 0.11.9 Fixed versions : 0.11.9, 0.11 nightly build 130, trunk nightly build 1434 **Description** mod_proxy65 is a file transfer proxy provided with Prosody to facilitate the transfer of files and other data between XMPP clients. It was discovered that the proxy65 component of Prosody allows open access by default, even if neither of the users have an XMPP account on the local server, allowing unrestricted use of the server's bandwidth. **Affected configurations** The default configuration does not enable mod_proxy65 and is not affected. With mod_proxy65 enabled, all configurations without a 'proxy65_acl' setting configured are affected. **Temporary mitigation** Configure 'proxy65_acl' to a list of XMPP domains that should be allowed to use the file transfer proxy. **Advice** All deployments should upgrade to 0.11.9 and/or configure a 'proxy65_acl' as desired. Deployments using nightly builds should upgrade to the latest available builds. The default behaviour in 0.11.9 allows all local clients to initiate a data stream through the proxy if proxy65_acl is unconfigured. **Credits** This flaw was discovered by the Prosody team. **Commits** - https://hg.prosody.im/trunk/rev/65dcc175ef5b -------------------------------------------------------------- 5/5: Undocumented dialback-without-dialback option insecure -------------------------------------------------------------- CVE : CVE-2021-32919 Affected versions : Prosody 0.10.x, Prosody 0.11.x prior to 0.11.9 Fixed versions : 0.11.9, 0.11 nightly build 130, trunk nightly build 1434 **Description** The undocumented option 'dialback_without_dialback' enabled an experimental feature for server-to-server authentication. A flaw in this feature meant it did not correctly authenticate remote servers, allowing a remote server to impersonate another server when this option is enabled. **Affected configurations** The default configuration is not affected. Configurations with the setting 'dialback_without_dialback' set to true are affected. **Temporary mitigation** Remove or disable the 'dialback_without_dialback' option. **Advice** All deployments should upgrade to 0.11.9 or disable this feature. Deployments using nightly builds should upgrade to the latest available builds. The affected feature has been removed in 0.11.9. **Credits** This flaw was discovered by the Prosody team. **Commits** - https://hg.prosody.im/trunk/rev/6be890ca492e - https://hg.prosody.im/trunk/rev/d0e9ffccdef9 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1182554] New: cannot start greetd.service .... missing PAM module
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1182554 Bug ID: 1182554 Summary: cannot start greetd.service .... missing PAM module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: denis.kondratenko(a)suse.com, mcepl(a)suse.com, opensuse(a)trummer.xyz, stdden(a)opensuse.org Found By: --- Blocker: --- Created attachment 846366 --> https://bugzilla.suse.com/attachment.cgi?id=846366&action=edit journalctl -xb output When trying to replace gdm with greetd following the steps on https://en.opensuse.org/Portal:OpenSUSEway, greetd fails to start and journal shows: �no 22 09:38:10 stitny greetd[2347]: error: PAM 'greetd' service missing When looking around, there is the file /usr/etc/pam.d/greetd with this content: ~@stitny$ cat /usr/etc/pam.d/greetd #%PAM-1.0 auth requisite pam_nologin.so auth include common-auth account include common-account password include common-password session required pam_loginuid.so session optional pam_keyinit.so force revoke session include common-session ~@stitny$ but I have still /etc/pam.d/ as well and there is no greetd file. Which one is used? -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1165273] New: zathura-plugin-pdf-mupdf not loaded due to error.
by bugzilla_noreply＠novell.com 31 Jan '23

31 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1165273 Bug ID: 1165273 Summary: zathura-plugin-pdf-mupdf not loaded due to error. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dracaphallus(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.100 Safari/537.36 Build Identifier: Running zathura after the installation of zathura-plugin-pdf-mupdf the following error output is produced: ``` error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so' (/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart). ``` >From the error output I'd deduced that the package was packaged wrong and therefore produced the error mentioned above. It has the plugin from working as intended by making zathura incapable of opening the supported document formats (PDF, ePub, and OpenXPS). This issue was reported 14 days ago using the comment section of openSUSE:Factory, while it was reported 8 days ago in the comment section of `X11:Utilities` with no response. This has lead me to file a bug report in OpenSUSE Bugzilla with the hope of getting this issue resolved. Reproducible: Always Steps to Reproduce: 1. Installing zathura-plugin-pdf-mupdf using zypper. 2. Running zathura through terminal. Actual Results: The following error was produced: ``` error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so' (/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart). ``` Expected Results: Zathura being able to open the supported document formats (PDF, ePub, and OpenXPS). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1188352] New: Can't enter LUKS password since kernel 5.13 on Pinebook Pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188352 Bug ID: 1188352 Summary: Can't enter LUKS password since kernel 5.13 on Pinebook Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jonasdcdm(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851029 --> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit dmesg Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt won't see it, it doesn't register any key press. Entering the password via serial console works, and the Pinebook Pro boots to the desktop, where the physical keyboard works again. Kernel 5.12.13-1 is still working fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1185174] New: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185174 Bug ID: 1185174 Summary: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848660 --> http://bugzilla.opensuse.org/attachment.cgi?id=848660&action=edit dmesg tail; journal tail; Xorg.0.log; drm.debug=0x06 log_buf_len=1M Original Summary: [i815] kernel 5.11: Xorg fails to run: open /dev/dri/card0: No such file or directory; (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) Xorg is running on TW20210420 on this ancient i815 Dell using xf86-video-intel DDX and kernel 5.10, but fails as indicated in summary with 5.11.15. https://www.linuxquestions.org/questions/linux-hardware-18/intel-corporatio… has a short record of TW Xorg on this same PC's IGP working 13 months ago. # inxi -CGSxxy System: Host: gx150 Kernel: 5.10.16-1-default i686 bits: 32 compiler: gcc v: 10.2.1 Desktop: KDE 3 wm: kwin dm: N/A Distro: openSUSE Tumbleweed 20210420 CPU: Info: Single Core model: Intel Pentium III bits: 32 type: MCP arch: P6 III Tualitin rev: 1 cache: L1: 32 KiB L2: 256 KiB flags: pae sse bogomips: 2259 Speed: 1130 MHz min/max: N/A Core speed (MHz): 1: 1130Graphics: Device-1: Intel 82815 Graphics vendor: Dell driver: N/A bus-ID: 00:02.0 chip-ID: 8086:1132 Display: x11 server: X.Org 1.20.10 driver: loaded: intel unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz s-dpi: 90 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 21.0.2 compat-v: 3.1 direct render: Yes # zypper se -si intel ... i | intel-vaapi-driver | package | 2.4.1-2.4 | i586 | OSS i+ | kernel-firmware-intel | package | 20210315-1.1 | noarch | OSS i | libdrm_intel1 | package | 2.4.105-1.1 | i586 | OSS i+ | xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-5.7 | i586 | OSS # rpm -qa | grep nel-def kernel-default-5.4.14-2.1.i586 OK kernel-default-5.5.13-1.1.i586 OK kernel-default-5.7.11-1.1.i586 OK kernel-default-5.8.15-1.2.i586 OK kernel-default-5.9.14-1.2.i586 OK kernel-default-5.10.16-1.3.i586 OK kernel-default-5.11.2-1.2.i586 FAIL kernel-default-5.11.15-1.2.i586 FAIL -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1179538] New: FAIL: gdb.arch/amd64-init-x87-values.exp: check_setting_mxcsr_before_enable: check new value of MXCSR is still in place
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179538 Bug ID: 1179538 Summary: FAIL: gdb.arch/amd64-init-x87-values.exp: check_setting_mxcsr_before_enable: check new value of MXCSR is still in place Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In more detail: ... (gdb) PASS: gdb.arch/amd64-init-x87-values.exp: check_setting_mxcsr_before_enable: step forward one instruction for mxcsr test p/x $mxcsr^M $1 = 0x1f80^M (gdb) FAIL: gdb.arch/amd64-init-x87-values.exp: check_setting_mxcsr_before_enable: check new value of MXCSR is still in place ... This is with kernel-obs-build-5.9.11-1.1. So the scenario is as follows: - we set mxcsr to a non-default value - then we stepi past a nop - we check that mxcsr still has the same value - it turns out, it doesn't: the register is back to default value It sounds alot like the fix for https://bugzilla.kernel.org/show_bug.cgi?id=207979 is active: ... commit 7ad816762f9bf89e940e618ea40c43138b479e10 Author: Petteri Aimonen <jpa(a)git.mail.kapsi.fi> Date: Tue Jun 16 11:12:57 2020 +0200 x86/fpu: Reset MXCSR to default in kernel_fpu_begin() ... However, the commit has been in place since v5.8, and I don't see this problem on a laptop with tumbleweed running kernel v5.9.10. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1173748] New: System hangups in dual monitor use, likely Plasma/Xorg related
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173748 Bug ID: 1173748 Summary: System hangups in dual monitor use, likely Plasma/Xorg related Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: P.Suetterlin(a)royac.iac.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am experiencing repeated issues with my laptop (running current TW, 20200701) when sitting in the dock with a second monitor connected. It usually starts with the second monitor going dark, then getting signal again (and the monitor displays the current input as info, so indeed the signal seems to have been gone?). Sometimes, it does stay black until I move the cursor in there and/or go to a workspace that has a window on that screen. Sometimes, in that situation where the monitor is black, moving the cursor to that screen doesn't help, but short after that the whole computer freezes dead. It also isn't pingable via network anymore, only 5s power button switchoff helps. I've seen it several times already over the last months, sometimes not for a longer time. With the current release I had it 2 times already, plus a coredump of kwin after a restart (the first coredump since many months) Unfortunately I never found anything in the logfiles after a lockup. And the system is configured not to write coredumps, so also nothing from the kwin crash :( In short, I don't really have a clue if that is software or hardware, or how to narrow it down, as I have so far not found a way to produce the issue. I *think* it is only happening after the monitors went to DPMS suspend, and with no window on the second monitor. Hardware is a Lenovo T460p, Skylake with HD530 graphics, and Xorg based KDE/Plasma. Maybe someone has an idea what to check/look for. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179894 Bug ID: 1179894 Summary: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com, okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com Depends on: 1178401 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1178401 +++ ## Observation https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o… shows repeated warnings about: ``` [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00… shows the same ## Expected result Only errors and warnings in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1178463 Bug ID: 1178463 Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843325 --> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit lsusb -vv With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of: ... [ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? ... The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell, except for these messages, all USB connected peripherals (keyboard, mouse, webcam) are working. Attaching lsusb -vv and dmesg output. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1188487] New: BUG: workqueue lockup
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188487 Bug ID: 1188487 Summary: BUG: workqueue lockup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started seeing this bug on my tumbleweed system: ... 2021-07-07T16:24:41.803560+02:00 lena kernel: [1053710.804959] CPU: 3 PID: 31988 Comm: gdb Tainted: G D 5.12.10-1-default #1 openSUSE Tumbleweed Message from syslogd@lena at Jul 19 16:18:29 ... kernel:[722585.589404] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for inted: G D 5.12.10-1-default #1 openSUSE Tumbleweed 2021-07-07T16:24:41.803561+02:00 lena kernel: [1053710.804964] Hardware name: LENOVO 20F5S0KF00/20F5S0KF00, BIOS R02ET73W (1.46 ) 01/08/2020 2021-07-07T16:24:41.803563+02:00 lena kernel: [1053710.804966] Call Trace: 2021-07-07T16:24:41.803564+02:00 lena kernel: [1053710.804971] dump_stack+0x76/0x94 2021-07-07T16:24:41.803566+02:00 lena kernel: [1053710.804978] bad_page.cold+0x9b/0xa0 2021-07-07T16:24:41.803567+02:00 lena kernel: [1053710.804983] get_page_from_freelist+0x739/0x13a0 2021-07-07T16:24:41.803568+02:00 lena kernel: [1053710.804990] __alloc_pages_nodemask+0x161/0x310 2021-07-07T16:24:41.803569+02:00 lena kernel: [1053710.804993] pagecache_get_page+0x14c/0x4f0 2021-07-07T16:24:41.803570+02:00 lena kernel: [1053710.805000] grab_cache_page_write_begin+0 7-07T16:24:41.803572+02:00 lena kernel: [1053710.805009] iomap_write_actor+0x9f/0x1a0 2021-07-07T16:24:41.803573+02:00 lena kernel: [1053710.805013] iomap_apply+0x111/0x2e0 2021-07-07T16:24:41.803575+02:00 lena kernel: [1053710.805015] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803576+02:00 lena kernel: [1053710.805020] iomap_file_buffered_write+0x5c/0x80 2021-07-07T16:24:41.803577+02:00 lena kernel: [1053710.805023] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803578+02:00 lena kernel: [1053710.805026] xfs_file_buffered_write+0xbd/0x2b0 [xfs] 2021-07-07T16:24:41.803579+02:00 lena kernel: [1053710.805122] ? _flat_send_IPI_mask+0x21/0x40 2021-07-07T16:24:41.803580+02:00 lena kernel: [1053710.805128] ? generic_exec_single+0x50/0xc0 2021-07-07T16:24:41.803582+02:00 lena kernel: [1053710.805133] ? smp_call_function_single_async+0x17/0x20 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805138] new_sync_write+0x11c/0x1b0 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805143] vfs_write+0x1b8/0x270 2021-07-07T16:24:41.803585+02:00 lena kernel: [1053710.805146] ksys_write+0x5f/0xe0 2021-07-07T16:24:41.803586+02:00 lena kernel: [1053710.805150] do_syscall_64+0x33/0x80 2021-07-07T16:24:41.803587+02:00 lena kernel: [1053710.805155] entry_SYSCALL_64_after_hwframe+0x44/0xae 2021-07-07T16:24:41.803588+02:00 lena kernel: [1053710.805159] RIP: 0033:0x7fc4b3b4539f 2021-07-07T16:24:41.803589+02:00 lena kernel: [1053710.805162] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 49 f9 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 4a f9 ff 48 2021-07-07T16:24:41.803590+02:00 lena kernel: [1053710.805167] RSP: 002b:00007fff61dfb5f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805171] RAX: ffffffffffffffda RBX: 0000000000001000 RCX: 00007fc4b3b4539f 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805174] RDX: 0000000000001000 RSI: 0000000001f9fe90 RDI: 000000000000000e 2021-07-07T16:24:41.803593+02:00 lena kernel: [1053710.805177] RBP: 0000000001f9fe90 R08: 0000000000000000 R09: 00007fff61dfbb30 2021-07-07T16:24:41.803594+02:00 lena kernel: [1053710.805180] R10: 0000000001a44440 R11: 0000000000000293 R12: 0000000000001000 2021-07-07T16:24:41.803596+02:00 lena kernel: [1053710.805182] R13: 00000000018442a0 R14: 0000000000001000 R15: 00007fc4b3c18700 ... This is with kernel: ... $ uname -a Linux lena 5.12.13-1-default #1 SMP Mon Jun 28 06:37:23 UTC 2021 (74bd8c0) x86_64 x86_64 x86_64 GNU/Linux ... It happens during a build and test run of gdb. I've updated and rebooted to kernel version 5.13.0-1-default, but ran into the same bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 5