| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
PR: bin/144300
Submitted by: arundel
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
Due to UFS insistence to pretend that device sector size is 512 bytes,
sector size is obtained from ioctl(DIOCGSECTORSIZE) for real devices,
and from the label otherwise. The file images without label have to
be made with 512 sector size.
In collaboration with: pho
Reviewed by: jeff
Tested by: bz, pho
|
|
|
|
|
|
|
|
|
|
|
| |
the fragment, and write the full block. Reading less might not work
due to device sector size bigger then size of direntries in the
last directory fragment.
Reported by: bz
In collaboration with: pho
Reviewed by: jeff
Tested by: bz, pho
|
|
|
|
|
|
| |
but there is problem unlinking the file, log a warning.
MFC after: 1 week
|
|
|
|
|
|
| |
<sys/un.h> including what's needed.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
1. The descriptor is the one we are listening on (not the one when we connect
as a client and not the one which is created on accept(2)).
2. Descriptor was created by us (PID matches with the PID stored on bind(2)).
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
| |
gcc's imperfections.
MFC after: 1 week
|
|
|
|
|
|
| |
values.
MFC after: 1 week
|
|
|
|
|
| |
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
| |
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
| |
resource is already running.
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
worker can ask the main privileged process to connect in worker's behalf
and then we can migrate descriptor using this socketpair to worker.
This is not really needed now, but will be needed once we start to use
capsicum for sandboxing.
MFC after: 1 week
|
|
|
|
|
|
| |
in r214692.
MFC after: 1 week
|
|
|
|
|
|
| |
anything.
MFC after: 1 week
|
|
|
|
|
|
| |
We don't want to log this in hastctl.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
proto_connection_{send,recv} and change them to return proto_conn
structure. We don't operate directly on descriptors, but on
proto_conns.
- Add wrap method to wrap descriptor with proto_conn.
- Remove methods to send and receive descriptors and implement this
functionality as additional argument to send and receive methods.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If timeout argument to proto_connect() is -1, then the caller needs to use
this new function to wait for connection.
This change is in preparation for capsicum, where sandboxed worker wants
to ask main process to connect in worker's behalf and pass descriptor
to the worker. Because we don't want the main process to wait for the
connection, it will start async connection and pass descriptor to the
worker who will be responsible for waiting for the connection to finish.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
Confirmed by: rwatson
MFC after: 1 week
|
|
|
|
|
|
|
| |
I found no way how to use CMSG_NXTHDR() macro on ia64 without alignment
warnings.
MFC after: 1 week
|
|
|
|
| |
Those lines are part of the (for now) unused functions.
|
|
|
|
|
|
|
| |
over UNIX domain sockets and socket pairs.
This is in preparation for capsicum.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
to syslog if we run in background.
- Asserts in proto.c that method we want to call is implemented and remove
dummy methods from protocols implementation that are only there to abort
the program with nice message.
MFC after: 1 week
|
|
|
|
|
|
| |
the function does and mark it with __dead2.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
When requesting a scan and one is already in progess, e.g. while in scan
state, we happily wait for a scan done notification. Though, this
notification might never be sent, e.g. if we are trying to find a network
to associate to and there is none. Instead of always waiting for a
notification just do so if a new scan has been started. For both cases the
scan cache is used to report available networks even if the content might
not be fresh.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
| |
is deferred for the time it takes to flush the TX queue. This work being
done the scan then is continued, but only if it is marked to do so. As
the 'ifconfig scan' request is meant to be used after the interface is
brought up, request a background scan by default. This behaviour is
already documented in manual page.
This fixes on possible case where 'ifconfig scan' hangs infinitely.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
Accepting connections and handshaking in secondary is still done before
dropping privileges. It should be implemented by only accepting connections in
privileged main process and passing connection descriptors to the worker, but
is not implemented yet.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
- chrooting to /var/empty (user hast home directory),
- setting groups to 'hast' (user hast primary group),
- setting real group id, effective group id and saved group id to 'hast',
- setting real user id, effective user id and saved user id to 'hast'.
At the end verify that those operations where successfull.
MFC after: 1 week
|
|
|
|
|
|
| |
descriptors are open.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
we expect to be open. Also assert that they point at expected type.
Because openlog(3) API is unable to tell us descriptor number it is using, we
have to close syslog socket, remember assert message in local buffer and if we
fail on assertion, reopen syslog socket and log the message.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
to handle them more gracefully.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
| |
Found with: procstat(1)
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
PJDLOG_RVERIFY() - always check expression and on false log the given message
and exit.
PJDLOG_RASSERT() - check expression when NDEBUG is not defined and on false log
given message and exit.
PJDLOG_ABORT() - log the given message and exit.
MFC after: 1 week
|
|
|
|
|
|
| |
file at will.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
so there are no surprises once we start chrooting or using capsicum.
MFC after: 1 week
|
|
|
|
|
|
| |
- Remove redundant newline at the end of the file.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
| |
Fix segfault when TargetAddress is missing or mis-spelled in config file.
|
|
|
|
|
|
| |
instead of supplying number of bits.
Submitted by: bde
|
|
|
|
|
|
|
|
| |
master process only and pass changes to the worker processes over control
socket. This removes access to global namespace in preparation for capsicum
sandboxing.
MFC after: 2 weeks
|