slirp: Handle error returns from sosendoob()v2.10.0-rc1v2.10.0-rc0

sosendoob() can return a failure code, but all its callers ignore it.
This is OK in sbappend(), as the comment there states -- we will try
again later in sowrite(). Add a (void) cast to tell Coverity so.
In sowrite() we do need to check the return value -- we should handle
a write failure in sosendoob() the same way we handle a write failure
for the normal data.

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/sbuf.c b/sbuf.c
index 8a0a6a9..01f9a46 100644
--- a/sbuf.c
+++ b/sbuf.c
@@ -88,7 +88,7 @@ void sbappend(struct socket *so, struct mbuf *m)
     if (so->so_urgc) {
         sbappendsb(&so->so_rcv, m);
         m_free(m);
-        sosendoob(so);
+        (void)sosendoob(so);
         return;
     }