• Bug#1100634: linux: Please enable CONFIG_KALLSYMS_ALL for arm64 kernel

    From Hastalavista_debian@21:1/5 to All on Sun Mar 16 14:30:01 2025
    XPost: linux.debian.kernel

    Source: linux
    Version: 6.1.129-1
    Severity: wishlist
    X-Debbugs-Cc: hastalavista_debian@murena.io

    Dear Maintainer,

    I wish to use LKRG (https://lkrg.org) on my RPi, but it reported error "LKRG requires
    CONFIG_KALLSYMS_ALL" when building, which is strange to me because I have never run
    into such problems on amd64 laptops. I checked config file of arm64 kernel 6.1.129 and indeed it didn't have CONFIG_KALLSYMS_ALL enabled.

    I wish Debian can have CONFIG_KALLSYMS_ALL enabled by default, so that security tools like LKRG can run.


    -- System Information:
    Debian Release: 12.10
    APT prefers stable-security
    APT policy: (500, 'stable-security'), (500, 'stable')
    Architecture: amd64 (x86_64)

    Kernel: Linux 6.1.0-31-amd64 (SMP w/8 CPU threads; PREEMPT)
    Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emanuele Rocca@21:1/5 to All on Mon Mar 17 16:00:02 2025
    XPost: linux.debian.kernel

    Hi,

    On 2025-03-16 01:20, Hastalavista_debian wrote:
    I wish to use LKRG (https://lkrg.org) on my RPi, but it reported error "LKRG requires
    CONFIG_KALLSYMS_ALL" when building, which is strange to me because I have never
    run
    into such problems on amd64 laptops. I checked config file of arm64 kernel 6.1.129 and indeed it didn't have CONFIG_KALLSYMS_ALL enabled.

    I wish Debian can have CONFIG_KALLSYMS_ALL enabled by default, so that security
    tools like LKRG can run.

    Makes sense. Also noteworthy, CONFIG_KALLSYMS_ALL is enabled on arm64 on
    at least Fedora/RHEL/SuSE too.

    MR opened: https://salsa.debian.org/kernel-team/linux/-/merge_requests/1419

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bastian Blank@21:1/5 to Emanuele Rocca on Wed Mar 19 20:10:03 2025
    XPost: linux.debian.kernel

    On Mon, Mar 17, 2025 at 03:47:11PM +0100, Emanuele Rocca wrote:
    Makes sense. Also noteworthy, CONFIG_KALLSYMS_ALL is enabled on arm64 on
    at least Fedora/RHEL/SuSE too.

    Please provide a justification.

    Bastian

    --
    There are some things worth dying for.
    -- Kirk, "Errand of Mercy", stardate 3201.7

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bastian Blank@21:1/5 to All on Wed Mar 19 20:10:01 2025
    XPost: linux.debian.kernel

    On Sun, Mar 16, 2025 at 01:20:28PM +0000, Hastalavista_debian wrote:
    I wish to use LKRG (https://lkrg.org) on my RPi, but it reported error "LKRG requires
    CONFIG_KALLSYMS_ALL" when building, which is strange to me because I have never
    run
    into such problems on amd64 laptops. I checked config file of arm64 kernel 6.1.129 and indeed it didn't have CONFIG_KALLSYMS_ALL enabled.

    I wish Debian can have CONFIG_KALLSYMS_ALL enabled by default, so that security
    tools like LKRG can run.

    I don't believe this is a good enough reason to enable this heavy
    setting. The settings tells:

    | Say N unless you really need all symbols, or kernel live patching.

    We ship a complete set of symbols in our debug package and this is
    enough for any debugging workflow.

    Requiring this set to be compiled into the kernel itself is a sign of
    tampering with the kernel itself.

    Bastian

    --
    I object to intellect without discipline; I object to power without constructive purpose.
    -- Spock, "The Squire of Gothos", stardate 2124.5

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emanuele Rocca@21:1/5 to Bastian Blank on Thu Mar 20 10:50:01 2025
    XPost: linux.debian.kernel

    On 2025-03-19 08:01, Bastian Blank wrote:
    On Mon, Mar 17, 2025 at 03:47:11PM +0100, Emanuele Rocca wrote:
    Makes sense. Also noteworthy, CONFIG_KALLSYMS_ALL is enabled on arm64 on
    at least Fedora/RHEL/SuSE too.

    Please provide a justification.

    - Needed for perf/kprobes/debug output
    - It's on by default on both x86 and arm64 upstream
    - The Debian kernel team enabled it already on amd64, no reason to unset
    it on arm64

    Additionally, not a justification per se but a useful data point, all
    other distros I checked have it on.

    https://lore.kernel.org/all/164167904946.16921.8215342846945528313.tip-bot2@tip-bot2/
    https://github.com/torvalds/linux/blob/master/arch/x86/configs/x86_64_defconfig#L28
    https://github.com/torvalds/linux/blob/master/arch/arm64/configs/defconfig#L31 https://salsa.debian.org/kernel-team/linux/-/blob/debian/latest/debian/config/amd64/config?ref_type=heads#L343

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)