http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@suse.com, | |msuchanek@suse.com, | |tiwai@suse.com --- Comment #1 from Takashi Iwai --- Sounds like a good idea. Not sure where vmlinux*.xz should be moved to, though. I thought crash utility required vmlinux, but it's obviously for debugging. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tonyj@suse.com --- Comment #3 from Takashi Iwai --- Maybe Tony knows of such? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c5 --- Comment #5 from Michal Suchanek --- The point here is if also -debuginfo package is needed it can be moved there or some other -debugwhatever. If there are tools that can work with the vmlinux only then those will break. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c7 --- Comment #7 from Michal Suchanek --- I don't think you need debuginfo for profiling. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c9 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@suse.com Flags| |needinfo?(mls@suse.com) --- Comment #9 from Michal Suchanek --- There is one last problem: If vmlinux is needed for debugging only how do we ensure it's installed with the debuginfo package if we package it separately? debuginfo packages are created automagically so it's difficult to inject additional dependencies or files. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c11 --- Comment #11 from Tony Jones --- (In reply to Michal Suchanek from comment #5)

If there are tools that can work with the vmlinux only then those will break.

Correct. Hence my previous comment about moving slowly here. It may well be that most of these have been converted over to the various /proc interfaces (when full debuginfo isn't needed) but we should check. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c13 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com --- Comment #13 from Jiri Slaby --- When I added support for xz compression of vmlinux in bug 1155921, I investigated and only kdump and crash read it. kdump only copies the image to /var/crash/... crash uncompresses it and reads symbols from there. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c15 --- Comment #15 from Tony Jones --- (In reply to Jiri Slaby from comment #13)

When I added support for xz compression of vmlinux in bug 1155921, I investigated and only kdump and crash read it.

Per comment 12, this is clearly not true. I don't thinking moving it to debuginfo is a good idea. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c17 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tonyj@suse.com) --- Comment #17 from Jiri Slaby --- (In reply to Tony Jones from comment #12)

# stap do_fork.stp semantic error: while resolving probe point: identifier 'kernel' at /home/tonyj/stap/do_fork.stp:1:7 source: probe kernel.function("_do_fork"){ ^

semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo] under '/lib/modules/4.12.14-197.34-default/build'

Hmm, I don't see this: # ll /boot/vmlinux* -rw-r--r-- 1 root root 10030200 Mar 9 14:20 /boot/vmlinux-5.5.7-1-default.xz # strace -fo bubak -e trace=%file stap -v b.stap Pass 1: parsed user script and 476 library scripts using 97296virt/88352res/6588shr/81884data kb, in 280usr/90sys/559real ms. Pass 2: analyzed script: 1 probe, 0 functions, 0 embeds, 0 globals using 119936virt/112752res/8172shr/104524data kb, in 1110usr/100sys/1225real ms. Pass 3: translated to C into "/tmp/stapcPCpg1/stap_81ae959f3a822f58c54b6ac1ed4df3ae_916_src.c" using 119936virt/113000res/8420shr/104524data kb, in 990usr/60sys/1066real ms. Pass 4: compiled C into "stap_81ae959f3a822f58c54b6ac1ed4df3ae_916.ko" in 16370usr/8760sys/37761real ms. Pass 5: starting run. do fork: no dwarf do fork: no dwarf ^Cdo fork: no dwarf Pass 5: run completed in 20usr/200sys/50435real ms. # grep '"/boot' bubak 24675 openat(AT_FDCWD, "/boot/System.map-5.5.7-1-default", O_RDONLY) = 3 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.debug", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/.debug/vmlinux-5.5.7-1-default.debug", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/.debug/vmlinux-5.5.7-1-default", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.debug", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/build/vmlinux-5.5.7-1-default.debug", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/build/vmlinux-5.5.7-1-default", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.debug", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 lstat("/boot", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 24675 lstat("/boot/vmlinux-5.5.7-1-default", 0x7ffc1e6778e0) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.gz", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.bz2", O_RDONLY) = -1 ENOENT (No such file or directory) 24675 openat(AT_FDCWD, "/boot/vmlinux-5.5.7-1-default.xz", O_RDONLY) = 3 So it can and does open .xz. Tony, do you have some old version of systemtap? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c19 --- Comment #19 from Tony Jones --- (In reply to Jiri Slaby from comment #18)

(In reply to Jiri Slaby from comment #17)

...

So it can and does open .xz. Tony, do you have some old version of systemtap?

Stap seems to use libelf to handle that and this was added there by commit 6ecdead8c0fbba51e8b2561e4d54dd7be3f69204 Author: Roland McGrath Date: Fri Feb 11 12:29:45 2011 -0800

libdwfl: Search for Linux kernel binaries with compression file name suffixes.

So xz should not be a problem. That said, I don't understand what your issue is. Something seems to be broken on your system.

I don't have an issue. The vmlinux I was using wasn't xz compressed and so systemtap wasn't decompressing it. Maybe it can decompress xz. My point was that you said only "kdump and crash read it [vmlinux]" which isn't true, systemtap also does. That is all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c21 --- Comment #21 from Tony Jones --- (In reply to Jiri Slaby from comment #20)

(In reply to Tony Jones from comment #19)

...

I don't have an issue. The vmlinux I was using wasn't xz compressed and so systemtap wasn't decompressing it. Maybe it can decompress xz.

My point was that you said only "kdump and crash read it [vmlinux]" which isn't true, systemtap also does. That is all.

Aaah. It also looks (from the source code) that libdw (elfutils) can read also vmlinuz if there is no vmlinux.

This wasn't working for me when I tried it, so I had to manually decompress the installed vmlinux. Possible I'm using too old an elfutils, or issue was elsewhere. Regardless, not relevant to this bug. I'll verify it works off-line. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c23 --- Comment #23 from Tony Jones --- (In reply to Jiri Slaby from comment #20)

Aaah. It also looks (from the source code) that libdw (elfutils) can read also vmlinuz if there is no vmlinux.

Our vmlinuz is stripped of all ELF symbol data. # eu-readelf -s /boot/vmlinux-5.5.7-1-default.xz | wc -l 122468 # eu-readelf -s /boot/vmlinuz | wc -l 0 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c25 --- Comment #25 from Tony Jones --- (In reply to Michal Suchanek from comment #24)

This is not the way to tell. You must first unpack it. You could 'prove' any rpm package is stripped of all symbols by running readelf on the rpm.

My understanding (as was Jiri's from looking at the code) is that libdw handles the unpacking. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c27 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1162581 --- Comment #27 from Michal Suchanek --- get_kernel_version is using vmlinux (see bug 1162581) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c29 --- Comment #29 from Takashi Iwai --- A separate *-vmlinux package would give another benefit: we can package the uncompressed vmlinux if its installation is optional. Some applications need the raw vmlinux file and user had to uncompress manually, and this step can be avoided. Though, I'm not sure how many such applications exist now... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166406 http://bugzilla.suse.com/show_bug.cgi?id=1166406#c31 --- Comment #31 from Michal Suchanek --- get_kernel_version does not work on 32bit arm without vmlinux -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1166406 Libor Pechacek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lpechacek@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1166406 https://bugzilla.suse.com/show_bug.cgi?id=1166406#c40 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags| |needinfo?(fvogt@suse.com) --- Comment #40 from Jiri Slaby --- So what's the status of this please? Is it still desired, can we proceed? Or is this wontfix? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1166406 https://bugzilla.suse.com/show_bug.cgi?id=1166406#c42 --- Comment #42 from Michal Suchanek --- To summarize - vmlinux cannot be moved to debuginfo package - changing the way debuginfo packages are generated is infeasible, and this would need substantial change - some tools need only vmlinux, not debuginfo, and forcing installation of debuginfo for those is a no-go - moving vmlinux into separate package is possible (on non-ppc) provided tools that assume vmlinux is present are fixed up (there are some additional binaries used exclusively for debugging - eg. the s390 boot stub, vdso?) - some of these tools are something like debug tools or performance measurement tools that can be fixed up as problems are found - some of these tools may be part of basesystem and it is critical that they work from the start on all platforms - complex dependencies can be used to fix up debug package installation on SLE15, on SLE12 this cannot be reasonably expected to work. -- You are receiving this mail because: You are on the CC list for the bug.