From: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, markmc@redhat.com, lcapitulino@redhat.com
Subject: [Qemu-devel] Bug in net/socket.c: info_str is overwritten
Date: Thu, 6 May 2010 10:42:10 -0300 [thread overview]
Message-ID: <x2w394cf6841005060642jf2df51f1l358dbdfd58a7a279@mail.gmail.com> (raw)
Hi there,
I'm working on the conversion of the 'info network' command do QMP,
and I think I've found some problems.
Running qemu like this: qemu -net socket,listen=:3333
In net/socket.c, the function net_socket_listen_init() [1] is called
and a listening socket is created. There is nothing registering this,
so when using 'info network' as is, no information about this
listening socket is shown.
When a connection is accepted, the handler net_socket_accept() calls
net_socket_fd_init(). If the socket is
UDP/multicast net_socket_fd_init() calls net_socket_fd_init_dgram, if
the socket is TCP it calls net_socket_fd_init_dgram_stream. [2]
In both cases the info_str string is written inside
net_socket_fd_init_(stream|dgram) [3], and after that, it is
overwritten on a subsequent
snprintf() in net_socket_accept() [4].
net_socket_fd_init_(stream|dgram) always puts into the info_str the fd
number, and this information is overwritten latter. So, is the fd
number
relevant to be transmitted over QMP? Right now this information is
being lost, IMHO.
Same thing happens when qemu is run as a client:
net_socket_connect_init() calls net_socket_fd_init_(dgram|stream) and
latter overwrites info_str.
[1] http://git.qemu.org/qemu.git/tree/net/socket.c#n375
[2] http://git.qemu.org/qemu.git/tree/net/socket.c#n336
[3] http://git.qemu.org/qemu.git/tree/net/socket.c#n310
[4] http://git.qemu.org/qemu.git/tree/net/socket.c#n369
next reply other threads:[~2010-05-06 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 13:42 Miguel Di Ciurcio Filho [this message]
2010-05-08 1:09 ` [Qemu-devel] Re: Bug in net/socket.c: info_str is overwritten Luiz Capitulino
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=x2w394cf6841005060642jf2df51f1l358dbdfd58a7a279@mail.gmail.com \
--to=miguel.filho@gmail.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=markmc@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).