nl_recvmsgs return code issue about libnl HOT 1 CLOSED

nl_recvmsg() eventually calls recvmsg() multiple times.

In non-blocking mode, recvmsg() returns 0 when there is nothing to read. From your question, it seems that when the remote side closes, recvmsg() may also return 0 -- thus, that situation is indistinguishable for nl_recv() and nl_recvmsgs(). What do you expect libnl to do about that? If you use non-blocking IO, you need to handle this via something like poll().

If you look at the code, you'll see that nl_recvmsgs() pretty much returns the error code that nl_recv(). But if recvmsg() returns 0, there is no error indicated.
That is, "nl_recvmsgs () should just return whatever nl_recv returns" is already the case.

Maybe you want to use instead nl_recvmsgs_report(), which is basically like nl_recvmsgs() but also returns the number of received messages. Thus you know whether there were any messages received.

from libnl.