On Mon, Feb 27, 2023 at 6:17 AM Eduard Zingerman <eddyz87@xxxxxxxxx> wrote: > > On Sun, 2023-02-26 at 03:03 +0200, Eduard Zingerman wrote: > > On Sat, 2023-02-25 at 20:50 +0000, Matt Bobrowski wrote: > > > Sorry Eduard, I replied late last night although the email bounced due > > > to exceeding the mail char limit. Let's try attaching a compressed > > > variant of the requested files, which includes the compiled kernel's > > > BTF and the kernel's config. > > > > Hi Matt, > > > > I tried using your config but still can't reproduce the issue. > > Will try to do it using debian 12 chroot tomorrow or on Monday. > > Hi Matt, > > Short update: > I've reproduced the issue with multiple STRUCT 'linux_binprm' BTF IDs > in Debian testing chroot, thank you for providing all details. > Attaching the instructions in the end of the email. > Need some time to analyze pahole behavior. > Try using [0] to pinpoint what actually is different between any two linux_binprm definitions. I've hacked up this "tool" last time I had to pinpoint where two BTF types diverge, maybe it will save you a bit of time as well. I'd like to put this functionality into btfdump ([1]), but I didn't get to it yet, unfortunately. [0] https://github.com/libbpf/libbpf-bootstrap/tree/btfdiff-hack [1] https://github.com/anakryiko/btfdump > Thanks, > Eduard > > -- > > host root: > mkdir bookworm > sudo debootstrap testing bookworm/ http://deb.debian.org/debian/ > sudo mount -t proc proc bookworm/proc/ > sudo mount -t sysfs sys bookworm/sys/ > sudo chroot bookworm/ /bin/bash > [...]
