From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2] syscalls/sendmmsg: add new test
Date: Tue, 23 Apr 2019 21:50:25 +0200 [thread overview]
Message-ID: <20190423195024.GA28637@dell5510> (raw)
In-Reply-To: <20190419210637.88522-1-smuckle@google.com>
Hi Steve,
> Known issues/questions:
> - This test occasionally gets stuck when the two messages get sent by
> separate sendmmsg calls. The two sendmmsg calls complete successfully
> but recvmmsg blocks indefinitely. I am not yet sure what would cause
> this.
> - I have not used tst_get_unused_port() because I'm unsure of how that
> function should be made available for both the new and old test API?
> I can just create a duplicate function but is there a cleaner way?
As I need tst_get_unused_port() as well, I've sent a patch to port it to new API
and available for both new and legacy API via TST_GET_UNUSED_PORT() macro [1].
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/patch/1089695/
next prev parent reply other threads:[~2019-04-23 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 21:06 [LTP] [RFC PATCH v2] syscalls/sendmmsg: add new test Steve Muckle
2019-04-23 19:50 ` Petr Vorel [this message]
2019-05-21 14:47 ` Cyril Hrubis
2019-07-23 12:31 ` Cyril Hrubis
2019-07-23 16:59 ` Steve Muckle
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=20190423195024.GA28637@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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