Le 30/04/2025 à 14:48, Colin Watson a écrit : > Could you drop --leak-check=full from the valgrind call, and instead add > --main-stacksize=67108864 (i.e. eight times the current value)? Then > provoke the bug again and send me the new valgrind output. Let's see if > that tells us something different.
Same output :-( Log attached. > Could I also get your /etc/ssh/sshd_config and /etc/ssh/sshd_config.d/* > files (of course you can edit out anything secret, but if you do then > please at least keep the structure)? The (unedited) config files are attached too
avril 30 17:04:05 odysseus systemd[1]: Started ssh.service - OpenBSD Secure Shell server. avril 30 17:04:16 odysseus sshd[1065529]: ==1065529== Memcheck, a memory error detector avril 30 17:04:16 odysseus sshd[1065529]: ==1065529== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. avril 30 17:04:16 odysseus sshd[1065529]: ==1065529== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info avril 30 17:04:16 odysseus sshd[1065529]: ==1065529== Command: /usr/lib/openssh/sshd-session -D -R avril 30 17:04:16 odysseus sshd[1065529]: ==1065529== avril 30 17:04:17 odysseus sshd-session[1065529]: Connection from 127.0.0.1 port 41080 on 127.0.0.1 port 22 rdomain "" avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== Cannot map memory to grow the stack for thread #1 to 0x1ffeffc000 avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== Process terminating with default action of signal 11 (SIGSEGV): dumping core avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== Access not within mapped region at address 0x1FFEFFCD78 avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== Cannot map memory to grow the stack for thread #1 to 0x1ffeffc000 avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== at 0x1BCBC9: glob0 (glob.c:476) avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== If you believe this happened as a result of a stack avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== overflow in your program's main thread (unlikely but avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== possible), you can try to increase the size of the avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== main thread stack using the --main-stacksize= flag. avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== The main thread stack size used in this run was 67108864. avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== HEAP SUMMARY: avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== in use at exit: 518,745 bytes in 5,557 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== total heap usage: 8,552 allocs, 2,995 frees, 1,232,651 bytes allocated avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== LEAK SUMMARY: avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== definitely lost: 128 bytes in 2 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== indirectly lost: 5,632 bytes in 2 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== possibly lost: 4,608 bytes in 2 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== still reachable: 508,269 bytes in 5,550 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== suppressed: 108 bytes in 1 blocks avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== Rerun with --leak-check=full to see details of leaked memory avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== For lists of detected and suppressed errors, rerun with: -s avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== could not unlink /tmp/vgdb-pipe-from-vgdb-to-1065529-by-root-on-??? avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== could not unlink /tmp/vgdb-pipe-to-vgdb-from-1065529-by-root-on-??? avril 30 17:04:17 odysseus sshd[1065529]: ==1065529== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-1065529-by-root-on-??? avril 30 17:04:17 odysseus systemd-coredump[1065568]: Process 1065529 (memcheck-amd64-) of user 0 terminated abnormally with signal 11/SEGV, processing... avril 30 17:04:17 odysseus systemd[1]: Started systemd-coredump@19-1065568-0.service - Process Core Dump (PID 1065568/UID 0). avril 30 17:04:18 odysseus systemd-coredump[1065569]: Resource limits disable core dumping for process 1065529 (memcheck-amd64-). avril 30 17:04:18 odysseus systemd-coredump[1065569]: [🡕] Process 1065529 (memcheck-amd64-) of user 0 terminated abnormally without generating a coredump. avril 30 17:04:18 odysseus systemd[1]: systemd-coredump@19-1065568-0.service: Deactivated successfully. avril 30 17:04:18 odysseus sshd[1065336]: error: session process 1065529 for connection from 127.0.0.1 to 127.0.0.1 killed by signal 11 avril 30 17:04:18 odysseus sshd[1065336]: srclimit_penalise: ipv4: new 127.0.0.1/32 active penalty of 90 seconds for penalty: caused crash
sshd_config.tar.gz
Description: application/gzip
