June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193278] OS doesn't detect properly two identical NVMe with the same UUID.
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1193278 https://bugzilla.suse.com/show_bug.cgi?id=1193278#c12 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #12 from Daniel Wagner <daniel.wagner(a)suse.com> --- Not much we can do here. Closing bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199925] [Build 20220524] LTP: preadv2 fails
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199925 https://bugzilla.suse.com/show_bug.cgi?id=1199925#c5 --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- You can avoid the executable stack with diff --git a/testcases/kernel/kvm/Makefile b/testcases/kernel/kvm/Makefile index 69a9946fe0f3..adab569528b9 100644 --- a/testcases/kernel/kvm/Makefile +++ b/testcases/kernel/kvm/Makefile @@ -50,11 +50,11 @@ include $(top_srcdir)/include/mk/generic_leaf_target.mk ifdef VERBOSE $(CC) $(GUEST_CPPFLAGS) $(GUEST_CFLAGS) $(GUEST_LDFLAGS) -o $*-payload.elf $^ $(GUEST_LDLIBS) objcopy -O binary -j .init.boot -j .text -j .data -j .init -j .preinit_array -j .init_array --gap-fill=0 $*-payload.elf $*-payload.bin - ld -r -T $(abs_srcdir)/linker/payload.lds --oformat=$(BIN_FORMAT) -o $@ $*-payload.bin + ld -z noexecstack -r -T $(abs_srcdir)/linker/payload.lds --oformat=$(BIN_FORMAT) -o $@ $*-payload.bin else @$(CC) $(GUEST_CPPFLAGS) $(GUEST_CFLAGS) $(GUEST_LDFLAGS) -o $*-payload.elf $^ $(GUEST_LDLIBS) @objcopy -O binary -j .init.boot -j .text -j .data -j .init -j .preinit_array -j .init_array --gap-fill=0 $*-payload.elf $*-payload.bin - @ld -r -T $(abs_srcdir)/linker/payload.lds --oformat=$(BIN_FORMAT) -o $@ $*-payload.bin + @ld -z noexecstack -r -T $(abs_srcdir)/linker/payload.lds --oformat=$(BIN_FORMAT) -o $@ $*-payload.bin @echo KVM_CC $(target_rel_dir)$@ endif @rm $*-payload.elf $*-payload.bin -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199925] [Build 20220524] LTP: preadv2 fails
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199925 https://bugzilla.suse.com/show_bug.cgi?id=1199925#c4 --- Comment #4 from Cyril Hrubis <chrubis(a)suse.com> --- (In reply to Petr Vorel from comment #3) I guess that the KVM payload code trips some safety check in rpmbuild. We should turn off that check. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199925] [Build 20220524] LTP: preadv2 fails
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199925 https://bugzilla.suse.com/show_bug.cgi?id=1199925#c3 --- Comment #3 from Petr Vorel <petr.vorel(a)suse.com> --- FYI even the latest test nsuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-Build20220531-jeos-ltp-syscalls@uefi_virtio-2G [1] (which is using package from factory [2]) is still using old unfixed version bf9678782 ("tst_test: Remove timeout stubs") due kvm_pagefault01 error [3]: [ 1058s] ltp.x86_64: E: executable-stack (Badness: 10000) /opt/ltp/testcases/bin/kvm_pagefault01 [ 1058s] The binary declares the stack as executable. Executable stack is usually an [ 1058s] error as it is only needed if the code contains GCC trampolines or similar [ 1058s] constructs which uses code on the stack. One common source for needlessly [ 1058s] executable stack cases are object files built from assembler files which don't [ 1058s] define a proper .note.GNU-stack section. ... [ 1058s] ---------------- Badness 10214 exceeds threshold 999, aborting. ---------------- (there are many errors, but this one is considered that serious that it breaks build). Can anybody advice me how to allow LTP being build with kvm_pagefault01 being included in the package? [1] https://openqa.opensuse.org/tests/2397961#next_previous [2] https://download.opensuse.org/repositories/benchmark:/ltp:/devel/openSUSE_F… [3] https://build.opensuse.org/package/live_build_log/benchmark:ltp:devel/ltp/o… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199925] [Build 20220524] LTP: preadv2 fails
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199925 https://bugzilla.suse.com/show_bug.cgi?id=1199925#c2 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Petr Vorel <petr.vorel(a)suse.com> --- Thanks for a report, upstream fixed this problem the same day you reported it in this ticket: beedc4211 ("preadv203: set max_runtime to 60s") https://github.com/linux-test-project/ltp/commit/beedc4211b2afddabf2469668b… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200097] New: Booting problems with Tumbleweed 32-bit installed on an external USB drive
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200097 Bug ID: 1200097 Summary: Booting problems with Tumbleweed 32-bit installed on an external USB drive Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: I have Tumbleweed installed on an external 250G drive. Tumbleweed 64-bit is working fine, and uses an encrypted LVM. Tumbleweed 32-bit is giving problems. It's root file system is unencrypted, but it uses "/home" and swap from the same encrypted LVM. Everything worked pretty well up through kernel 5.15.x. But I have been having problems with 5.16 and 5.17 kernels. It is possible that this is actually a dracut issue (missing module). Background: I mostly use this with a KVM virtual machine (i.e. using "libvirt"). I normally start the VM, then click ESC to get a boot menu. I then plug in the USB external drive, and restart the machine (often with sending it CTRL-ALT-DEL). I again use the ESC key to get a boot menu and select the entry for the USB device. The kernel is loaded, and there is a message recognizing the USB drive. But often it stops there with no further progress. If I wait long enough (several minutes) I see dracut timeout messages. It looks as if the system is unable to access what is on that drive. Sometimes it boots normally. In that case, may 1-2 seconds after I see that initial screen, I am prompted for the LUKS password. But when it does not boot normally, I am never prompted for that LUKS password. I have attempted to setup up a similarly configured system in a separate VM, without using that external drive. And that works just fine. It seems that the problem is related to the USB external drive, with the USB being redirected from the KVM host machine to the VM. The KVM host is running Leap 15.4. If I instead try booting this on my laptop, so that the external drive is connected to a real machine rather than a VM, then everything seems to work normally. I never have problems with 64-bit Tumbleweed, on the same external drive. It is only with 32-bit Tumbleweed that I have problems. If I first boot into 32-bit Tumbleweed, and then reboot to 32-bit Tumbleweed (without shutting down the machine), then that usually works. But if my first boot is to 32-bit Tumbleweed, that usually fails. Reproducible: Sometimes -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1199618] [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199618 https://bugzilla.suse.com/show_bug.cgi?id=1199618#c1 --- Comment #1 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-ltp-syscalls@aarch64-HD24G https://openqa.opensuse.org/tests/2396570#step/fanotify16/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket. -- You are receiving this mail because: You are the assignee for the bug.

1 0