Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 5fbc00a3 | 2024-05-23 14:53:13 | event_warn mmap format | ||
| 6d125f54 | 2024-05-06 15:28:48 | Fix evbuffer_file_segment_new 64-bit support on Win32 (#1637) This fixes the problematic #define fstat _fstat which would only support files up to 2 GB. Also refactored it as evutil_fd_filesize to avoid exposing stat when not necessary. | ||
| 539f73e3 | 2024-02-20 09:30:22 | Fix leak in evbuffer_add_file() on empty files Found by oss-fuzz, after coverage had been improved in google/oss-fuzz#11257 v2: adjust test v3: fix for windows (_get_osfhandle() crashes when called on closed fd) v4: fix for EVENT__DISABLE_MM_REPLACEMENT | ||
| ed35b30f | 2023-10-23 16:52:19 | Fix two compiler errors for unused variable and undefined function In buffer.c a variable "flags" and a label "done" are defined but never used if "EVENT__HAVEMMAP" is not defined. The code does not work on platforms which do not provide the function `socketpair()`. Introduce EVENT__HAVE_SOCKETPAIR flag which determines if `socketpair()` or `evutil_ersatz_socketpair()` is used. | ||
| 55899c2f | 2024-01-14 21:24:37 | Use read/write instead of readv/writev for single buffer The `readv`/`writev` functions are designed for scattered I/O optimally, their logic in the kernel is more sophisticated, compared to read/write, which includes extra on-stack `iovec` in the kernel space, importing `iovec` array from user space to kernel space, reading/writing with `iov_iter`, etc. As a result, using `readv`/`writev` on single-segment `iovec` will fall into the special branch in the kernel where it is imported as `ITER_UBUF` differed from `ITER_IOVEC` for multiple-segments `iovec`. Thus, it is just not worth calling `readv`/`writev` for single-segment `iovec`, we should use `read`/`write` instead, to save it from going through the sophisticated yet unnecessary kernel code path, circumvent a waste of kernel on-stack memory, copying `iovec` between user space and kernel space, etc. | ||
| 4c38de8c | 2023-11-26 20:52:32 | Fix -Walloc-size (#1526) Co-authored-by: Azat Khuzhin <azat@libevent.org> | ||
| a579b1d7 | 2023-10-20 15:36:07 | Fix compile error in evbuffer_read() The variable chainp is only used if USE_IOVEC_IMPL is defined. This makes a strict compiler complain about unused variables, since chainp is declared outside of an USE_IOVEC_IMPL block. | ||
| 648ec50e | 2023-09-21 15:13:31 | Add function evbuffer_add_reference_with_offset() This is the same as evbuffer_add_reference(), but allows to specify offset in the @data v2: rename evbuffer_add_reference_misalign() to evbuffer_add_reference_with_offset() | ||
| 0b79a002 | 2023-01-02 17:06:48 | buffer: use pread() for evbuffer_file_segment_materialize() If pread(2) is available, prefer it over double lseek(2) and read(2) in evbuffer_file_segment_materialize(). Signed-off-by: Dmitry Antipov <dantipov@cloudlinux.com> | ||
| 99fd68ab | 2022-08-07 13:51:48 | Add check of mmap64 function and use it when available rather that mmap There can be issues on 32-bit architectures to mmap 2+GiB file, and to make this portable between different version of glibc, mmap64 was prefered over _FILE_OFFSET_BITS |