From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: libtirpc List <libtirpc-devel@lists.sourceforge.net>
Cc: vasily Isaenko <vasily.isaenko@oracle.com>,
ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] svc_vc_create/clnt_vc_create and RPC_ANYFD
Date: Tue, 25 Mar 2014 19:35:20 +0400 [thread overview]
Message-ID: <5331A238.3020003@oracle.com> (raw)
Hi!
Sorry, but yet another question regarding rpc-tirpc-full-test-suite.
Some binaries from this suite pass RPC_ANYFD to svc_vc_create() or
clnt_vc_create().
Like this one -
https://github.com/linux-test-project/ltp/blob/master/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/tirpc_svc_5/tirpc_svc_5.c
:
transp = svc_vc_create(RPC_ANYFD, 1024, 1024);
And, of course, the tests using this fail.
I dig into the libtirpc sources and didn't found anything that could
state that we may pass RPC_ANYFD to these functions.
From svc_vc_create() comments:
"The filedescriptor passed in is expected to refer to a bound, but
not yet connected socket."
and from clnt_vc_create():
"fd should be an open socket"
So invoking svc_vc_create(RPC_ANYFD,...) or clnt_vc_create(RPC_ANYFD,
...) is incorrect. Right?
Thank you.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2014-03-25 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 15:35 Stanislav Kholmanskikh [this message]
2014-03-25 15:56 ` [LTP] [Libtirpc-devel] svc_vc_create/clnt_vc_create and RPC_ANYFD Chuck Lever
2014-03-26 6:58 ` Stanislav Kholmanskikh
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=5331A238.3020003@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.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