| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
o getsockopt(SO_ACCEPTFILTER) always returns success on listen socket
even we didn't install accept filter on the socket.
o Fix these bugs and add regression tests for them.
Submitted by: Igor Sysoev [1]
Reviewed by: alfred
MFC after: 2 weeks
|
|
|
|
| |
Update copyright.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
intended to verify that SIGPIPE is delivered to a process writing or
sending on a socket that has been shut down for write. If available,
SO_NOSIGPIPE is also tested.
This regression test is currently passed by RELENG_4, but not by HEAD or
RELENG_5, due to a bug in the write() code for sockets. SO_NOSIGPIPE is not
present in RELENG_4, however, so is not tested there.
Reported by: Mikko Tyolajarvi <mbsd at pacbell dot net>
PR: 78478
|
|
|
|
|
|
| |
bind()/connect() system calls, which is intended to confirm that the
right successes and errors occur when rendezvousing via the file system
name space.
|
|
|
|
|
|
| |
settings can override local ones.
Pointed out by: ru
|
|
|
|
|
| |
already associated datagram unix domain socket by issuing connect() system
call.
|
|
|
|
| |
OK'ed by: core
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
understood by Perl's Test::Harness module and prove(1) commands.
Update README to describe the new protocol. The work's broken down into
two main sets of changes.
First, update the existing test programs (shell scripts and C programs)
to produce output in the ok/not ok format, and to, where possible, also
produce a header describing the number of tests that are expected to be
run.
Second, provide the .t files that actually run the tests. In some cases
these are copies of, or very similar too, scripts that already existed.
I've kept the old scripts around so that it's possible to verify that
behaviour under this new system (in terms of whether or not a test fails)
is identical to the behaviour under the old system.
Add a TODO file.
|
|
|
|
|
|
|
|
| |
performs a non-blocking connect from another socket, and then closes
the listen socket rather than accepting. This is intended to
exercise the close path in which connections are aborted due to a
close on the listen socket while the connection is in the listen
queue.
|
|
|
|
| |
any fake value.
|
|
|
|
| |
Suggested by: ru (some time ago)
|
|
|
|
| |
Suggested by: ru (some time ago)
|
|
|
|
|
| |
just "FAIL" output, in order to make it consistent with other tests in
the regression test tree.
|
| |
|
|
|
|
|
| |
holding the value O_NONBLOCK. This worked previously because I was
lucky.
|
|
|
|
| |
compiler line.
|
|
|
|
|
| |
it into accept(). Depending on the initial value in memory, it is
otherwise possible to get EINVAL.
|
|
|
|
|
|
| |
elementary exercising of kqueues on datagram and stream sockets. Note
that the datagram write kqueue case is left untested due to potentially
confusing behavior for the developer (me) that might require attention.
|
|
|
|
|
| |
(and close) PF_UNIX socket pairs, and that we can't create PF_INET
socket pairs. More tests to follow.
|
|
|
|
|
|
| |
filter to an inet socket and check at various points during the socket
life cycle that the filter can or cannot be attached, and that once
attached that the right one is attached and that it can be queried.
|
|
accept() returns EAGAIN on a non-blocking listen socket. This is the
tool I used to check that such a bug was resolved when merging accept()
locking.
|