From: Steve Sistare <steven.sistare@oracle.com>
To: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Cc: Steve Sistare <steven.sistare@oracle.com>
Subject: [PATCH] tap: fix net_init_tap() return code
Date: Tue, 4 Apr 2023 09:00:04 -0700 [thread overview]
Message-ID: <1680624004-154390-1-git-send-email-steven.sistare@oracle.com> (raw)
When net_init_tap() succeeds for a multi-queue device, it returns a
non-zero ret=1 code to its caller, because of this code where ret becomes
1 when g_unix_set_fd_nonblocking succeeds. Luckily, the only current call
site checks for negative, rather than non-zero.
ret = g_unix_set_fd_nonblocking(fd, true, NULL);
if (!ret) {
...
goto free_fail;
Also, if g_unix_set_fd_nonblocking fails (though unlikely), ret=0 is returned,
and the caller will use a broken interface.
Fixes: a8208626ba89.. ("net: replace qemu_set_nonblock()")
Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
---
net/tap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/tap.c b/net/tap.c
index 1bf085d..1f3e927 100644
--- a/net/tap.c
+++ b/net/tap.c
@@ -906,8 +906,8 @@ int net_init_tap(const Netdev *netdev, const char *name,
goto free_fail;
}
- ret = g_unix_set_fd_nonblocking(fd, true, NULL);
- if (!ret) {
+ if (!g_unix_set_fd_nonblocking(fd, true, NULL)) {
+ ret = -1;
error_setg_errno(errp, errno, "%s: Can't use file descriptor %d",
name, fd);
goto free_fail;
--
1.8.3.1
next reply other threads:[~2023-04-04 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 16:00 Steve Sistare [this message]
2023-04-04 22:00 ` [PATCH] tap: fix net_init_tap() return code Philippe Mathieu-Daudé
2023-04-05 15:38 ` Steven Sistare
2023-04-11 6:32 ` Jason Wang
2023-04-11 13:10 ` Steven Sistare
2023-04-13 6:57 ` Jason Wang
-- strict thread matches above, loose matches on Subject: below --
2025-07-14 20:36 Steve Sistare
2025-07-14 22:31 ` Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1680624004-154390-1-git-send-email-steven.sistare@oracle.com \
--to=steven.sistare@oracle.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).