qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ed Swierk <eswierk@aristanetworks.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] slirp: Remove our_addr code
Date: Wed, 22 Jul 2009 18:37:34 -0700	[thread overview]
Message-ID: <1248313054.14831.36.camel@localhost.localdomain> (raw)

Three problems with our_addr:

- It's determined only once when qemu starts, but the address can change
(just like the DNS configuration can).

- It's supposed to be the IP address of a host network interface, but
there's no guarantee that gethostbyname(gethostname()) actually does
that: the host might be a laptop that has only a loopback interface up,
or the hostname might be localhost.localdomain, etc.

- It's useless: aside from the CU-SeeMe protocol emulation which I
propose removing, the only other reference is in get_dns_addr(), but
can't imagine why you would want to send DNS requests to a different IP
address if you're running a DNS server on the host and resolv.conf
points to 127.0.0.1.

These problems are easily solved by removing the code.

Signed-off-by: Ed Swierk <eswierk@aristanetworks.com>

---
diff --git a/slirp/main.h b/slirp/main.h
index e87b068..8d09df9 100644
--- a/slirp/main.h
+++ b/slirp/main.h
@@ -30,7 +30,6 @@ extern char *slirp_tty;
 extern char *exec_shell;
 extern u_int curtime;
 extern fd_set *global_readfds, *global_writefds, *global_xfds;
-extern struct in_addr our_addr;
 extern struct in_addr loopback_addr;
 extern char *username;
 extern char *socket_path;
diff --git a/slirp/slirp.c b/slirp/slirp.c
index 3214c29..aead5b0 100644
--- a/slirp/slirp.c
+++ b/slirp/slirp.c
@@ -26,8 +26,6 @@
 #include "slirp.h"
 #include "hw/hw.h"
 
-/* host address */
-struct in_addr our_addr;
 /* host loopback address */
 struct in_addr loopback_addr;
 
@@ -129,8 +127,6 @@ int get_dns_addr(struct in_addr *pdns_addr)
         if (sscanf(buff, "nameserver%*[ \t]%256s", buff2) == 1) {
             if (!inet_aton(buff2, &tmp_addr))
                 continue;
-            if (tmp_addr.s_addr == loopback_addr.s_addr)
-                tmp_addr = our_addr;
             /* If it's the first one, set it to dns_addr */
             if (!found) {
                 *pdns_addr = tmp_addr;
@@ -164,8 +160,6 @@ int get_dns_addr(struct in_addr *pdns_addr)
 static void slirp_init_once(void)
 {
     static int initialized;
-    struct hostent *he;
-    char our_name[256];
 #ifdef _WIN32
     WSADATA Data;
 #endif
@@ -181,17 +175,6 @@ static void slirp_init_once(void)
 #endif
 
     loopback_addr.s_addr = htonl(INADDR_LOOPBACK);
-
-    /* FIXME: This address may change during runtime */
-    if (gethostname(our_name, sizeof(our_name)) == 0) {
-        he = gethostbyname(our_name);
-        if (he) {
-            our_addr = *(struct in_addr *)he->h_addr;
-        }
-    }
-    if (our_addr.s_addr == 0) {
-        our_addr = loopback_addr;
-    }
 }
 
 static void slirp_state_save(QEMUFile *f, void *opaque);

             reply	other threads:[~2009-07-23  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  1:37 Ed Swierk [this message]
2009-07-23  1:41 ` [Qemu-devel] Re: [PATCH] slirp: Remove our_addr code Ed Swierk
2009-07-23  6:51   ` Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2009-08-01  1:10 [Qemu-devel] " Ed Swierk

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=1248313054.14831.36.camel@localhost.localdomain \
    --to=eswierk@aristanetworks.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).