status: split off error messages into a new 'peer_status' type.

Several daemons (onchaind, hsm) want to use the status messages, but
don't communicate with peers.  The coming changes made them drag in
more code they didn't need, so instead we have a different
non-overlapping type.

We combine the status_received_errmsg and status_sent_errmsg
into a single status_peer_error, with the presence or not of the
'error_for_them' field indicating direction. 

We also rename status_fatal_connection_lost() to
peer_failed_connection_lost() to fit in.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2018-02-19 11:36:15 +10:30
parent 65ff5f8bb1
commit f76ff90485
17 changed files with 156 additions and 145 deletions

View File

@@ -22,4 +22,14 @@ void peer_failed_(int peer_fd, int gossip_fd,
const struct channel_id *channel_id,
const char *fmt, ...)
PRINTF_FMT(6,7) NORETURN;
/* We're failing because peer sent us an error message */
void peer_failed_received_errmsg(int peer_fd, int gossip_fd,
struct crypto_state *cs, u64 gossip_index,
const char *desc,
const struct channel_id *channel_id) NORETURN;
/* I/O error */
void peer_failed_connection_lost(void) NORETURN;
#endif /* LIGHTNING_COMMON_PEER_FAILED_H */