From: Cyril Hrubis <chrubis@suse.cz>
To: Chuck Ebbert <cebbert.lkml@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] recvfrom01: fix test for invalid message flags
Date: Mon, 27 Oct 2014 11:20:13 +0100 [thread overview]
Message-ID: <20141027102013.GA9534@rei.suse.de> (raw)
In-Reply-To: <20141001171032.698f1356@as>
Hi!
> The recv tests were making invalid assumptions about how flags are
> checked by the kernel. (It makes no explicit tests for invalid flags
> or combinations of flags.) [1] So the current method of setting every
> possible flag and checking for a specific error is not valid.
>
> Before kernel 3.17 we were effectively just testing having the MSG_OOB
> flag set with no out-of-band data available. With 3.17 and later we
> were testing having MSG_ERRQUEUE set with no error data available,
> which returns a different error (and causes the existing test to fail).
>
> Replace the bogus test for invalid flags with two new tests that check
> return codes for invalid MSG_OOB and MSG_ERRQUEUE flags.
>
> Note that this introduces a failure on kernels before 3.17, which has
> a bug fix for MSG_ERRQUEUE flag handling. This failure is a legitimate
> bug on these older kernels. (They should not be returning success with
> no data available.)
Sorry for the delay, acked, tested and pushed, thanks.
Will you also send similar patches for the rest of the recv testcases?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-10-27 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 22:10 [LTP] recvfrom01: fix test for invalid message flags Chuck Ebbert
2014-10-27 10:20 ` Cyril Hrubis [this message]
2014-11-26 11:38 ` Cyril Hrubis
2015-01-06 10:07 ` Jan Stancek
2015-01-08 10:43 ` Cyril Hrubis
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=20141027102013.GA9534@rei.suse.de \
--to=chrubis@suse.cz \
--cc=cebbert.lkml@gmail.com \
--cc=ltp-list@lists.sourceforge.net \
/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