diff options
author | Stefano Brivio <sbrivio@redhat.com> | 2024-10-25 00:29:50 +0200 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2024-10-30 12:37:31 +0100 |
commit | 099ace64cedbf43922527dc7f132f0c0e65f308a (patch) | |
tree | c664b12fbb6f3ea1cc8fed211756221b6b918cf4 /udp.c | |
parent | 59fe34ee36368bb28c8298b1a1bfad5d0d9f47a3 (diff) | |
download | passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar.gz passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar.bz2 passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar.lz passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar.xz passt-099ace64cedbf43922527dc7f132f0c0e65f308a.tar.zst passt-099ace64cedbf43922527dc7f132f0c0e65f308a.zip |
treewide: Address cert-err33-c clang-tidy warnings for clock and timer functions
For clock_gettime(), we shouldn't ignore errors if they happen at
initialisation phase, because something is seriously wrong and it's
not helpful if we proceed as if nothing happened.
As we're up and running, though, it's probably better to report the
error and use a stale value than to terminate altogether. Make sure
we use a zero value if we don't have a stale one somewhere.
For timerfd_gettime() and timerfd_settime() failures, just report an
error, there isn't much else we can do.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'udp.c')
0 files changed, 0 insertions, 0 deletions