| commit | 2fdafe7ae253f1e6caadc2ca1fcacfecca8b11d1 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Tue Oct 04 02:30:23 2016 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 29 07:14:52 2021 |
| tree | 2abb5eeb2dda9b68fc5217a00d850f14a0247522 | |
| parent | 0f84527af0d2f527eb9dfb908eb70a958b96c185 [diff] |
daisydog: use O_CLOEXEC This should make no practical difference. This is more about using the flag consistently in the codebase whenever we don't need the leaky semantics. BUG=None TEST=CQ passes Change-Id: I16c68fdd1c99481dbc3fe283e0e63aefee7f6e25 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/daisydog/+/2658415 Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Mike Frysinger <vapier@chromium.org>
GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/
The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:
Daisy Dogs are not persnickety little ankle biters
When this daisydog doesn't run, the machine should reset. :)
An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270
The watchdog project is alot more complicated than what the Chromium OS project needs.