From: Marcelo Henrique Cerri <marcelo.cerri@canonical.com>
To: shuah <shuah@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/net: replace AF_MAX with INT_MAX in socket.c
Date: Tue, 17 Sep 2019 04:12:22 -0300 [thread overview]
Message-ID: <20190917071222.6nfzmcxt4kxzgpki@gallifrey> (raw)
In-Reply-To: <212adcf8-566e-e06d-529f-f0ac18bd6a35@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
So the problem arises because the headers we have in userspace might
be older and not match what we have in the kernel. In that case, the
actual value of AF_MAX in the userspace headers might be a valid
protocol family in the new kernel.
That happens relatively often for us because we support different
kernel versions at the same time in a given Ubuntu series.
An alternative is to use the headers we have in the kernel tree, but I
believe that might cause other issues.
On Mon, Sep 16, 2019 at 10:09:13AM -0600, shuah wrote:
> On 9/16/19 9:03 AM, Marcelo Henrique Cerri wrote:
> > Use INT_MAX instead of AF_MAX, since libc might have a smaller value
> > of AF_MAX than the kernel, what causes the test to fail.
> >
> > Signed-off-by: Marcelo Henrique Cerri <marcelo.cerri@canonical.com>
> > ---
> > tools/testing/selftests/net/socket.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/net/socket.c b/tools/testing/selftests/net/socket.c
> > index afca1ead677f..10e75ba90124 100644
> > --- a/tools/testing/selftests/net/socket.c
> > +++ b/tools/testing/selftests/net/socket.c
> > @@ -6,6 +6,7 @@
> > #include <sys/types.h>
> > #include <sys/socket.h>
> > #include <netinet/in.h>
> > +#include <limits.h>
> > struct socket_testcase {
> > int domain;
> > @@ -24,7 +25,10 @@ struct socket_testcase {
> > };
> > static struct socket_testcase tests[] = {
> > - { AF_MAX, 0, 0, -EAFNOSUPPORT, 0 },
> > + /* libc might have a smaller value of AF_MAX than the kernel
> > + * actually supports, so use INT_MAX instead.
> > + */
> > + { INT_MAX, 0, 0, -EAFNOSUPPORT, 0 },
> > { AF_INET, SOCK_STREAM, IPPROTO_TCP, 0, 1 },
> > { AF_INET, SOCK_DGRAM, IPPROTO_TCP, -EPROTONOSUPPORT, 1 },
> > { AF_INET, SOCK_DGRAM, IPPROTO_UDP, 0, 1 },
> >
>
> What failure are you seeing? It sounds arbitrary to use INT_MAX
> instead of AF_MAX. I think it is important to understand the
> failure first.
>
> Please note that AF_MAX is widely used in the kernel.
>
> thanks,
> -- Shuah
--
Regards,
Marcelo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-17 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 15:03 [PATCH] selftests/net: replace AF_MAX with INT_MAX in socket.c Marcelo Henrique Cerri
2019-09-16 16:09 ` shuah
2019-09-17 7:12 ` Marcelo Henrique Cerri [this message]
2019-09-17 14:09 ` shuah
2019-09-23 8:51 ` David Miller
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=20190917071222.6nfzmcxt4kxzgpki@gallifrey \
--to=marcelo.cerri@canonical.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).