| Age | Commit message (Collapse) | Author |
|---|
|
some tweaks.
With feedback and ok jmc@
|
|
ok jmc@, benno@, "yes" deraadt@
|
|
found with regress/usr.bin/mandoc/db/dbm_dump;
OK jmc@
|
|
this has no effect except to make ktrace output prettier.
ok bluhm mpi
|
|
event_pending, evtimer_pending, and signal_pending all write to the
timeval because that's how they tell the caller when the event is
meant to fire.
ok deraadt@ millert@ jmc@ schwarze@
|
|
the string buffer.
ok jsing millert
|
|
OK bluhm@ nicm@
|
|
Avoids inconsistent capitalization of libevent at start of sentence
suggested by and ok jmc@, ok bluhm@
|
|
correctly - logically complete that now by removing MLINKS from base;
authors need only to ensure there is an entry in NAME for any function/
util being added. MLINKS will still work, and remain for perl to ease
upgrades;
ok nicm (curses) bcook (ssl)
ok schwarze, who provided a lot of feedback and assistance
ok tb natano jung
|
|
idioms.
Adopt the more concise fcntl(n, F_GETFL) over fcntl(n, F_GETFL, 0)
where it is obvious further investigation will not yield and
even better way.
Obviousness evaluation and ok guenther@
|
|
tcpbench (at a minimum) relies on the old behavior of changes all happening
after all event handlers run. in particular, it resets the event for the
listening socket *before* calling accept(), when it is still readable.
kevent then (correctly) says it is readable on the next go through the loop.
silly, subtle, and stupid.
problem reported by kettenis
|
|
of deferring until the dispatch loop. kqueue support for various types
of files and filesystems has been historically incomplete, and kevent
handles this condition by returning an error. the libevent dispatch
loop has no way to recover from this error and fails catastrophically,
bringing down the entire process because one file went bad.
now, instead of all that happending, event_add will return an error. the
application can choose to handle or ignore this error, but at least the
band will play on.
ok nicm
|
|
|
|
or otherwise change Dt to reflect the name of an existing function;
feedback/ok schwarze
|
|
|
|
|
|
argument names, from Fabian Raetz. ok deraadt
|
|
|
|
a use after free if the callback has freed the ev. With F in
malloc.conf both tmux and the regression tests triggered a segmentation
fault.
OK nicm@
|
|
- Avoid deadlock when activating signals. Fixes bug 3048812.
Based on patch by Nicholas Marriott.
The deadlock was ultimately fixed in a different way (by disabling
reinit - see event.c r1.25). Add it now for consistency but without
the Windows compatibility code. Convert the fnctl() calls to
SOCK_CLOEXEC | SOCK_NONBLOCK to simplify the code.
OK nicm@
|
|
- Defensive programming to prevent (hopefully impossible) stack-stomping
OK nicm@
|
|
- https://github.com/libevent/libevent/commit/7b21c4eabf1f3946d3f63cce1319c490caab8ecf
- For this fix, we need to make sure that passing too-large inputs to
the evbuffer functions can't make us do bad things with the heap.
On top of that do:
- Update libevent version to 1.4.15-stable.
- Use SIZE_MAX from limits.h instead of a private define.
- Do not declare 'size_t need' twice to avoid a compiler warning.
OK sthen
|
|
switch fprintf(stderr) over to event_warn() on malloc failure. fix
up an errant newline in an existing event_warn while there.
originally i just wanted to delete the fprintf
diff from nicm@ who is away from a keyboard right now so cant commit
guenther@ agrees with the idea
|
|
|
|
|
|
|
|
trying to check what's missing;
|
|
|
|
|
|
from schwarze@
|
|
from schwarze@
|
|
from schwarze again
|
|
represent newlines still.
|
|
|
|
evbuffers, not evbufbuffers.
|
|
.Fo evbuffer_readln
.Fa "struct evbuffer *buf"
.Fa "size_t *read_out"
.Fa "enum evbuffer_eol_style eol_style"
.Fc
is more readable mdoc for very long prototypes than lines like
.Fn "evbuffer_readln" "struct evbuffer *buf" "size_t *read_out" "enum evbuffer_eol_style eol_style"
|
|
evbuffer_foo functions do. reyk, nicm, jmc, and schwarze seem to
support a manpage as a reasonable solution to this problem.
im putting this in a separate manpage because i find they get too
cumbersome when they get too big. ingo agrees (and suggests even
this might be too big).
the file is evbuffer_new.3 rather than evbuffer.3 because we document
functions.
ok reyk@ nicm@ jmc@ schwarze@
this is rough, everyone has tweaks coming.
|
|
|
|
them anymore, but evutil is still part of libevent's interface.
Separate the API of evutil from libevent and do not include evutil.h
from event.h automatically. A version bump is not necessary as the
library itself does not change.
Bulk ports build done by landry@ had no fallout.
OK nicm@ deraadt@
|
|
All warnings have been fixed in libevent.
OK nicm@
|
|
OK nicm@
|
|
derived from size_t and passed to functions as size_t parameters.
Change them from int to size_t to avoid compiler warnings.
OK doug@ nicm@
|
|
useless. Let libevent call the libc functions directly.
OK nicm@
|
|
OK nicm@
|
|
OK nicm@
|
|
OK nicm@
|
|
OK nicm@
|
|
backends.
OK nicm@
|
|
OK nicm@
|
|
Do not include sys/param.h.
OK nicm@
|
