linux-ext4 - [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-217965-13602-15c2DJjrxL@https.bugzilla.kernel.org/>
Date: Fri, 17 Nov 2023 00:01:28 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

https://bugzilla.kernel.org/show_bug.cgi?id=217965

--- Comment #32 from Eyal Lebedinsky (bugzilla@...l.emu.id.au) ---
Looks like a basic misunderstanding on my side, or maybe more preparation is
needed? What am I missing?

$ sudo perf probe -a "ext4_mb_find_good_group_avg_frag_lists order"
Failed to find the path for the kernel: Invalid ELF file
  Error: Failed to add events.

$ uname -a
Linux e7.eyal.emu.id.au 6.5.10-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Nov 
2 19:59:55 UTC 2023 x86_64 GNU/Linux

$ ls -l /boot/*6.5.10*
-rw------- 1 root root  8727059 Nov  2 11:00
/boot/System.map-6.5.10-200.fc38.x86_64
-rw-r--r-- 1 root root   264245 Nov  2 11:00
/boot/config-6.5.10-200.fc38.x86_64
-rw------- 1 root root 39368262 Nov  9 10:55
/boot/initramfs-6.5.10-200.fc38.x86_64.img
lrwxrwxrwx 1 root root       46 Nov  9 10:55
/boot/symvers-6.5.10-200.fc38.x86_64.xz ->
/lib/modules/6.5.10-200.fc38.x86_64/symvers.xz
-rwxr-xr-x 1 root root 14551752 Nov  2 11:00
/boot/vmlinuz-6.5.10-200.fc38.x86_64

I strace'd the command, and toward the end I see this (I have vmlinuz, not
vmlinux - related?).
These are the first failed 'openat()' in the trace.

openat(AT_FDCWD, "vmlinux", O_RDONLY)   = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/boot/vmlinux", O_RDONLY) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/boot/vmlinux-6.5.10-200.fc38.x86_64", O_RDONLY) = -1 ENOENT
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/boot/vmlinux-6.5.10-200.fc38.x86_64",
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/modules/6.5.10-200.fc38.x86_64/build/vmlinux", O_RDONLY)
= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/lib/modules/6.5.10-200.fc38.x86_64/vmlinux",
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/boot/vmlinux-6.5.10-200.fc38.x86_64.debug",
O_RDONLY) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD,
"/root/.debug/.build-id/d3/6a8ae40f88e310401726e275aa1940b279babd",
{st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
openat(AT_FDCWD,
"/root/.debug/.build-id/d3/6a8ae40f88e310401726e275aa1940b279babd/kallsyms",
O_RDONLY) = 3

Earlier I see this open success:

newfstatat(AT_FDCWD, "/lib/modules/6.5.10-200.fc38.x86_64/vmlinuz",
{st_mode=S_IFREG|0755, st_size=14551752, ...}, 0) = 0

which is identical to the one in /boot.

Should I boot a different kernel type?

Remember that I am not a dev...

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.