From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: synnefo-devel@googlegroups.com,
Stratos Psomadakis <psomas@grnet.gr>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] iotests: Send the correct fd in socket_scm_helper
Date: Fri, 12 Sep 2014 10:31:17 +0200 [thread overview]
Message-ID: <20140912083117.GB5076@noname.redhat.com> (raw)
In-Reply-To: <87sijx1fqx.fsf@blackfin.pond.sub.org>
Am 12.09.2014 um 09:04 hat Markus Armbruster geschrieben:
> Stratos Psomadakis <psomas@grnet.gr> writes:
>
> > Make sure to pass the correct fd via SCM_RIGHTS in socket_scm_helper.c
> > (i.e. fd_to_send, not socket-fd).
> >
> > Signed-off-by: Stratos Psomadakis <psomas@grnet.gr>
> > Signed-off-by: Dimitris Aragiorgis <dimara@grnet.gr>
Thanks, applied to the block branch.
(Also thanks to Markus for copying me, would have missed the patch
otherwise.)
> > tests/qemu-iotests/socket_scm_helper.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tests/qemu-iotests/socket_scm_helper.c b/tests/qemu-iotests/socket_scm_helper.c
> > index 0e2b285..8195983 100644
> > --- a/tests/qemu-iotests/socket_scm_helper.c
> > +++ b/tests/qemu-iotests/socket_scm_helper.c
> > @@ -52,7 +52,7 @@ static int send_fd(int fd, int fd_to_send)
> > cmsg->cmsg_len = CMSG_LEN(sizeof(int));
> > cmsg->cmsg_level = SOL_SOCKET;
> > cmsg->cmsg_type = SCM_RIGHTS;
> > - memcpy(CMSG_DATA(cmsg), &fd, sizeof(int));
> > + memcpy(CMSG_DATA(cmsg), &fd_to_send, sizeof(int));
> >
> > do {
> > ret = sendmsg(fd, &msg, 0);
>
> Ouch. Do you have an idea what's broken without this fix?
As far as I can tell, nothing. Test case 045 will send a different file
descriptor than it intended to, but the file descriptors aren't used
other than checking whether qemu correctly reports their existence, so
it doesn't matter.
I'm not adding qemu-stable therefore. Please correct me if I'm missing
something.
Kevin
next prev parent reply other threads:[~2014-09-12 8:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:19 [Qemu-devel] [PATCH 0/2] Monitor-related fixes Stratos Psomadakis
2014-09-11 15:19 ` [Qemu-devel] [PATCH 1/2] monitor: Reset HMP mon->rs on CHR_EVENT_CLOSED Stratos Psomadakis
2014-09-12 6:58 ` Markus Armbruster
2014-09-12 13:53 ` [Qemu-devel] [synnefo-devel] " Stratos Psomadakis
2014-09-12 14:07 ` [Qemu-devel] [PATCH resend " Stratos Psomadakis
2014-09-12 15:21 ` Luiz Capitulino
2014-09-12 17:01 ` [Qemu-devel] [synnefo-devel] " Stratos Psomadakis
2014-09-12 17:19 ` Luiz Capitulino
2014-09-13 16:27 ` Stratos Psomadakis
2014-09-14 1:23 ` Luiz Capitulino
2014-09-15 12:34 ` [Qemu-devel] [PATCH resend v2 1/2] monitor: Reset HMP mon->rs in CHR_EVENT_OPEN Stratos Psomadakis
2014-09-15 14:23 ` Luiz Capitulino
2014-09-11 15:19 ` [Qemu-devel] [PATCH 2/2] iotests: Send the correct fd in socket_scm_helper Stratos Psomadakis
2014-09-12 7:04 ` Markus Armbruster
2014-09-12 8:31 ` Kevin Wolf [this message]
2014-09-12 13:47 ` Stratos Psomadakis
2014-09-12 6:49 ` [Qemu-devel] [PATCH 0/2] Monitor-related fixes Markus Armbruster
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=20140912083117.GB5076@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=psomas@grnet.gr \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=synnefo-devel@googlegroups.com \
/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).