From cbbd17e3f4e460f410d59cbb1523ae0b25d130d8 Mon Sep 17 00:00:00 2001 From: Daniel Willmann Date: Wed, 17 May 2023 17:08:10 +0200 Subject: osmo_io: Support detecting non-blocking connect() libosmo-netif does a non blocking connect(), which as per definition of the socket API is signalled from the OS to the user by marking the file descriptor writable. osmo_io needs to signal this somehow. Previously osmo_io would only call the write_cb if actual data has been sent. This patch changes the behaviour so that calling osmo_iofd_write_enable() will call write_cb() on a writable socket even if the write queue is empty. Change-Id: I893cbc3becd5e125f2f06b3654578aed0aacadf3 --- tests/osmo_io/osmo_io_test.ok | 1 + 1 file changed, 1 insertion(+) (limited to 'tests') diff --git a/tests/osmo_io/osmo_io_test.ok b/tests/osmo_io/osmo_io_test.ok index 745e36a8..43e5464f 100644 --- a/tests/osmo_io/osmo_io_test.ok +++ b/tests/osmo_io/osmo_io_test.ok @@ -1,5 +1,6 @@ Running test_connected ep1: write() returned rc=16 +ep2: write() returned rc=0 ep2: read() msg with len=16 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 Running test_unconnected -- cgit v1.2.3