From c4760b306a06a8fe3c6690002f6b54bd3cfa9449 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Mon, 29 Sep 2025 12:26:14 +0930 Subject: [PATCH] ccan/io: fix misleading comment in previous commit. We don't need to be duplex to have this problem: the write side does it too in the example I found. Signed-off-by: Rusty Russell --- ccan/io/io.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/ccan/io/io.c b/ccan/io/io.c index 178ab01b..baa9a497 100644 --- a/ccan/io/io.c +++ b/ccan/io/io.c @@ -584,11 +584,8 @@ struct io_plan *io_sock_shutdown(struct io_conn *conn) return io_close(conn); /* We need to make sure we don't try to write again, so - * "wait" on something which will never be woken. - * - * In the duplex case, we can call io_sock_shutdown on the - * input side, while io_write is going on on the output side. - * Then we will try to write, fail, and immediately close. */ + * "wait" on something which will never be woken: otherwise + * we will try to write, fail, and immediately close. */ return io_wait_dir(conn, io_sock_shutdown, IO_OUT, io_never, NULL); } -- 2.47.3