netdev - Re: pull-request: bpf 2024-07-25

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] [day] [month] [year] [list]
Message-ID: <804E813B-9F16-486F-9E92-EB8B3F84C5CB@meta.com>
Date: Thu, 25 Jul 2024 19:47:04 +0000
From: Manu Bretelle <chantra@...a.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Daniel Borkmann <daniel@...earbox.net>,
        "davem@...emloft.net"
	<davem@...emloft.net>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        Alexei Starovoitov
	<ast@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Martin KaFai Lau
	<martin.lau@...ux.dev>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "bpf@...r.kernel.org" <bpf@...r.kernel.org>
Subject: Re: pull-request: bpf 2024-07-25



> On Jul 25, 2024, at 11:40 AM, Jakub Kicinski <kuba@...nel.org> wrote:
> 
> 
> 
> On the LLVM19 I see this in all outputs:
> ar: libLLVM.so.19.0: cannot open shared object file: No such file or directory
> 
> But presumably that's harmless, then.

Oh I see. It seems this is only affecting gcc builds.

Seem that nm/ar are not affected:

# ldd /usr/bin/ar /usr/bin/nm
/usr/bin/ar:
        linux-vdso.so.1 (0x00007fffa7376000)
        libbfd-2.34-system.so => /lib/x86_64-linux-gnu/libbfd-2.34-system.so (0x00007f6e90609000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6e90417000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6e903fb000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6e903f5000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f6e9076e000)
/usr/bin/nm:
        linux-vdso.so.1 (0x00007ffd817ad000)
        libbfd-2.34-system.so => /lib/x86_64-linux-gnu/libbfd-2.34-system.so (0x00007f09dc4ab000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f09dc2b9000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f09dc29d000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f09dc297000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f09dc60c000)


but the “llvm” versions are:

# ldd /usr/bin/llvm-ar /usr/bin/llvm-nm
/usr/bin/llvm-ar:
        linux-vdso.so.1 (0x00007ffd675b2000)
        libLLVM.so.19.0 => not found
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe0ba21d000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe0ba03b000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe0b9eec000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe0b9ed1000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe0b9cdf000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fe0ba260000)
/usr/bin/llvm-nm:
        linux-vdso.so.1 (0x00007ffecd6ea000)
        libLLVM.so.19.0 => not found
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ffadeb05000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ffade923000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffade7d4000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ffade7b9000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffade5c7000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ffadeb5a000)



Seems the llvm package rom llvm repo shadows the one from the repo, installing libllvm19 as a side effect but not updating the ld conf path .

# dpkg -l | grep llvm
ii  libllvm19:amd64                       1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies, runtime library
ii  llvm                                  1:19.0-58~exp2+0~20240303102334.17~1.gbp3b61b3                amd64        Low-Level Virtual Machine (LLVM)
ii  llvm-19                               1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies
ii  llvm-19-dev                           1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies, libraries and headers
ii  llvm-19-linker-tools                  1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies - Plugins
ii  llvm-19-runtime                       1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies, IR interpreter
ii  llvm-19-tools                         1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64        Modular compiler and toolchain technologies, tools
ii  llvm-runtime:amd64                    1:19.0-58~exp2+0~20240303102334.17~1.gbp3b61b3                amd64        Low-Level Virtual Machine (LLVM), bytecode interpreter

Seems everything works so far. Going to cross fingers that it holds.

Manu