Hello Jenkins Builder,

I'd like you to reexamine a change. Please visit

https://gerrit.osmocom.org/c/osmo-e1d/+/32386

to look at the new patch set (#2).

Change subject: proto_clnt: close osmo-e1d control socket on connection loss ......................................................................

proto_clnt: close osmo-e1d control socket on connection loss

When osmo-e1d is terminated the socket file descriptor on the client side will get permanent POLLHUP events. This means that the registered callback gets called with flags OSMO_FD_READ but the received data will be of length zero. We must detect this situations and close the file descriptor on connection loss. Otherwise we would get called over and over again in an endless loop, resulting in 100% CPU usage.

Related: OS#5983 Change-Id: Ib849e0ec1a1cca77eb588076d1d2201594b5c568 --- M src/proto_clnt.c 1 file changed, 22 insertions(+), 1 deletion(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-e1d refs/changes/86/32386/2