The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: lkml <linux-kernel@vger.kernel.org>
Subject: recvfrom01, recvmsg01 LTP failures on 2.5
Date: 04 Dec 2002 14:10:10 -0600	[thread overview]
Message-ID: <1039032611.3497.91.camel@plars> (raw)

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

At some point between 2.5.46 and 2.5.47, the LTP tests for recvfrom01
and recvmsg01 began to fail.  The test common to both that is failing is
passing fromlen == -1.  Calling recvfrom or recvmsg like this passes on
2.4 and 2.5.46, but returns -EINVAL on 2.5.47 and later.  If this was
intentional, I could understand it since that is certainly an invalid
argument for fromlen, but I would like to have that confirmed, and know
what the plans are for backporting that to 2.4.  I'll probably be
changing the test before the next ltp release (should be on Dec. 10),
but it will just flipflop from the test failing on 2.5 all the time to
failing on 2.4 all the time.

Thanks,
Paul Larson

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]

                 reply	other threads:[~2002-12-04 20:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1039032611.3497.91.camel@plars \
    --to=plars@linuxtestproject.org \
    --cc=linux-kernel@vger.kernel.org \
    /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