>/dev/kmsg can return EPIPE when messages was dropped after the fd was
>opened.
That is an unfortunate choice, forcing syslogd to trap SIGPIPE for
*reading*.
My conclusion is not "sanitize_read should be changed", it is
"sanitize_read should not be used when reading from /dev/kmsg". 😛
And even then, can reading on /dev/kmsg even return EOF? If it cannot,
there is no possible confusion either.
Device files are such a bunch of ad-hoc cases, it's annoying.
--
Laurent
Received on Wed Jul 01 2026 - 04:19:59 CEST