From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] libc-test contribution
Date: Fri, 16 Aug 2024 13:00:35 -0400 [thread overview]
Message-ID: <20240816170034.GT10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <20240816155729.GS10433@brightrain.aerifal.cx>
On Fri, Aug 16, 2024 at 11:57:29AM -0400, Rich Felker wrote:
> On Fri, Aug 16, 2024 at 09:35:38AM +0200, Szabolcs Nagy wrote:
> > * Ward, Ryan C <ryan.c.ward3@boeing.com> [2024-08-16 01:06:55 +0000]:
> > > Hello,
> > >
> > > I would like to start contributing some test cases to libc-test. I have
> > > started with testing some simple recent regressions (e.g. a test for
> > > the recent fix commit 947b4574), and am aiming to start filling in
> > > missing functional test coverage. Am I able to submit the test
> > > directly to this mailing list, and are there any other immediate
> > > areas of libc-test that need implementation?
> >
> > this list is fine
> >
> > there are many areas missing
> > but they need test infrastucture
> > eg networking tests depending on
> > /etc/resolv.conf need to run in
> > a separate mount namespace.
>
> I could try writing a helper module to do this. Basically it would
> just unshare into a new user+mount+network namespace and, if
> /etc/resolv.conf exists, bind-mount an empty file over it. Then you
> can bind port 53 and it will intercept all queries, and you don't have
> to worry about anything going out to the real network or having
> network-dependent behaviors.
Something like this:
#define _GNU_SOURCE
#include <stdio.h>
#include <unistd.h>
#include <sched.h>
#include <sys/mount.h>
#include <fcntl.h>
#include <stdlib.h>
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <net/if.h>
#include <netinet/in.h>
int enter_dns_test_ns()
{
if (unshare(CLONE_NEWUSER|CLONE_NEWNS|CLONE_NEWNET) < 0)
return -1;
int s = socket(AF_INET, SOCK_DGRAM, IPPROTO_IP);
if (s < 0) return -1;
struct ifreq ifr = {
.ifr_name = "lo",
.ifr_addr = (union { struct sockaddr_in sin; struct sockaddr sa; }){{
.sin_family = AF_INET,
.sin_port = 0,
.sin_addr = htonl(0x7f000001),
}}.sa,
};
if (ioctl(s, SIOCSIFADDR, &ifr) < 0)
return -1;
if (ioctl(s, SIOCGIFFLAGS, &ifr) < 0)
return -1;
ifr.ifr_flags |= IFF_UP;
if (ioctl(s, SIOCSIFFLAGS, &ifr) < 0)
return -1;
char tmp[] = "/tmp/emptyXXXXXX";
int fd = mkostemp(tmp, O_CLOEXEC);
if (fd < 0) return -1;
int r = mount(tmp, "/etc/resolv.conf", 0, MS_BIND, 0);
unlink(tmp);
return r;
}
prev parent reply other threads:[~2024-08-16 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 1:06 Ward, Ryan C
2024-08-16 7:35 ` Szabolcs Nagy
2024-08-16 15:57 ` Rich Felker
2024-08-16 17:00 ` Rich Felker [this message]
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=20240816170034.GT10433@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).