diff options
| author | Glenn Washburn <[email protected]> | 2022-03-03 01:53:33 -0600 |
|---|---|---|
| committer | Richard Weinberger <[email protected]> | 2022-03-11 10:56:17 +0100 |
| commit | 82017457957a550d7d00dde419435dd74a890887 (patch) | |
| tree | c7a5ec0332ae472c2c6b98dd39a66ac154aefbe8 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 3cb5a7f167c620a8b0e38b0446df2e024d2243dc (diff) | |
um: run_helper: Write error message to kernel log on exec failure on host
The best place to log errors from the host side is in the kernel log within
the UML guest. Letting the user now that exec() failed and why is very
helpful when the user is trying to determine why some aspect of UML is not
working. For instance, when telneting into the UML instance, if the
connection is established and then immediately dropped, this may be due to
exec() failing because in.telnetd is not found.
Signed-off-by: Glenn Washburn <[email protected]>
Signed-off-by: Richard Weinberger <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions