On Wed, Sep 24, 2014 at 09:05:30AM -0500, Chuck Ebbert wrote: > Three of those failures were invalid assumptions about kernel behavior > with every possible flag set. [2] > > [2] http://marc.info/?t=141148149900006&r=1&w=2
A simple fix for LTP would be for the recv/recvfrom/recvmsg tests to check for EINVAL on kernel 3.16 and older, and EAGAIN on 3.17 and newer, but something feels wrong about this, since, according to the linux-netdev discussion, the actual error returned is undefined. So maybe the tests should not check for a specific error, but just any error in general when passing invalid flags? -- Jeff Bastian ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
