Closed 13r0ck closed 12 months ago
I'm not sure if this is the right thread. What should we - safely - do whit this? Maybe delete? or wait next release?
Thanks, Regards
/arch/:
x86
/arch/x86:
entry include tools
/arch/x86/entry:
syscalls
/arch/x86/entry/syscalls:
/arch/x86/include:
generated
/arch/x86/include/generated:
asm uapi
/arch/x86/include/generated/asm:
syscalls_32.h
/arch/x86/include/generated/uapi:
asm
/arch/x86/include/generated/uapi/asm:
bpf_perf_event.h errno.h fcntl.h ioctl.h ioctls.h ipcbuf.h param.h poll.h resource.h socket.h sockios.h termbits.h termios.h types.h unistd_32.h unistd_64.h unistd_x32.h
/arch/x86/tools:
relocs relocs_32.o relocs_64.o relocs_common.o
@ziprasidone146939277 at this point it is best to wait for this to be released. The extra files arn't going to hurt anything, just some source code.
I have been unable to recreate this issue. I'm wondering if this is still necessary? If so is there a known way to reproduce it to test against?
6.1.11 might be the kernel that was broken, this is likely not necessary anymore though
Some mysterious directories started to show up in user's root
/arch
for example.This appears to be due to an upstream packaging change of
linux-libc-dev
. This reverts that.