mirror of
https://git.busybox.net/busybox
synced 2026-01-31 16:43:21 +00:00
480a07bd68
When `fstat` fails, `st` is left uninitialised. In our case, Ben Kohler noticed our release media builds were failing in Gentoo on x86 when building busybox with occasional SIGBUS. This turned out to be EOVERFLOW (from 32-bit ino_t) which wasn't being reported because nothing was checking the return value from `fstat`. Fix that to avoid UB (use of uninit var) and to give a more friendly error to the user. This actually turns out to be fixed already in the kernel from back in 2010 [0] and 2016 [1]. [0] |
||
|---|---|---|
| .. | ||
| basic | ||
| kconfig | ||
| bb_release | ||
| bloat-o-meter | ||
| checkhelp.awk | ||
| checkstack.pl | ||
| cleanup_printf2puts | ||
| echo.c | ||
| embedded_scripts | ||
| find_bad_common_bufsiz | ||
| find_stray_common_vars | ||
| find_stray_empty_lines | ||
| fix_ws.sh | ||
| gcc-version.sh | ||
| gen_build_files.sh | ||
| generate_BUFSIZ.sh | ||
| Kbuild.include | ||
| Kbuild.src | ||
| Makefile.build | ||
| Makefile.clean | ||
| Makefile.host | ||
| Makefile.IMA | ||
| Makefile.lib | ||
| memusage | ||
| mkconfigs | ||
| mkdiff_obj | ||
| mkdiff_obj_bloat | ||
| mkmakefile | ||
| objsizes | ||
| randomtest | ||
| randomtest.loop | ||
| sample_pmap | ||
| showasm | ||
| test_make_clean | ||
| test_make_O | ||
| test_setenv_leak.c | ||
| trylink | ||