| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
macOS always fills in si_code for SIG{BUS,ILL,SEGV} as if it were a real
hardware fault, so returning from the handler is not guaranteed to re-
trigger the signal.
Fixes: aecdabb ("sighook: Return instead of re-raising for faults")
Link: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/2386463/4/util/posix/signals_test.cc
Link: https://github.com/chromium/crashpad/commit/e0d8a0aa01ac176804077f1f128ccc894c098f79
|
| |
|
|
|
|
| |
Link: https://savannah.gnu.org/bugs/index.php?45930
|
| |
|
|
|
|
|
| |
This wraps __sanitizer_annotate_contiguous_container() to give
byte-precise tracking of usable allocation sizes with ASan.
|
|
|
|
|
| |
It's probably nicer to avoid evaluating expensive arguments when not
sanitizing, rather than relying on the optimizer to clean them up.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cross-platform-actions/action](https://github.com/cross-platform-actions/action) from 0.25.0 to 0.26.0.
- [Release notes](https://github.com/cross-platform-actions/action/releases)
- [Changelog](https://github.com/cross-platform-actions/action/blob/master/changelog.md)
- [Commits](https://github.com/cross-platform-actions/action/compare/v0.25.0...v0.26.0)
---
updated-dependencies:
- dependency-name: cross-platform-actions/action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The new ioq_submit() function is now necessary to call to ensure the
pending request batch is flushed.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This helps avoid situations where multiple waiters block on different
slots using the same monitor, which happened more often than expected
due to correlations caused by batching.
|
|
|
|
|
| |
Also, cache-align struct ioq_ent to avoid false sharing when two workers
are handling neighbouring requests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the death look exactly like it would if we didn't handle the
signal at all. Coredumps will point at the right instruction, segfaults
will get logged in dmesg again, etc.
Technically POSIX says this is undefined, but if we get a fault, we've
already done something undefined anyway ;)
Link: https://github.com/rust-lang/rust/issues/26458
|
|
|
|
| |
QNX doesn't support SA_RESTART.
|
| |
|
| |
|
|
|
|
|
|
| |
QNX's qcc, for example, will complain that
cc1: error: command-line option '-pthread' is valid for the driver but not for C
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 4 to 5.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/codecov/codecov-action/compare/v4...v5)
---
updated-dependencies:
- dependency-name: codecov/codecov-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
| |
This allows us to build against liburing as old as version 2.0, which is
apparently shipped by the latest Amazon Linux distribution.
Fixes: https://github.com/tavianator/bfs/issues/147
|
|
|
|
|
| |
We might want to change the size of an allocated region without changing
which bytes are initialized.
|
| |
|
| |
|
|
|
|
|
|
|
| |
In trie_remove(), clearing the bit before trie_node_collapse() causes us
to free the old node with size 1 instead of 2, putting it on the wrong
freelist. This is technically safe with the current arena
implementation, but not intentional.
|
|
|
|
|
|
|
|
|
| |
Allowing unaligned sizes will allow us to allocate aligned slabs with
additional metadata in the tail without ballooning the allocation size
for large alignments.
Link: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2244.htm#dr_460
Link: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2072.htm
|
| |
|
|\
| |
| | |
Fix bfs coloring all files as if they had a capability, on non-Linux systems
|
|/
|
|
|
|
|
|
|
|
|
| |
On non-Linux systems, bfs_check_capabilities always returned -1, so
cpath_has_capabilities would always return true. If bfs was called with
an LS_COLORS containing the `ca` statement, e.g. `ca=30;41`, bfs would
color ALL the files. While including the `ca` statement in LS_COLORS
on non-Linux systems is unusual, this is not an error and is a valid
use-case (e.g. Using GNU ls or lsd).
Fixes: 1520d4d3 ("color: Don't color files like directories on ENOTDIR")
|
|
|
|
| |
Fixes: https://github.com/tavianator/bfs/issues/145
|
|
|
|
| |
Link: https://savannah.gnu.org/bugs/?66365
|
|\
| |
| | |
Fix typo in manpage
|
|/ |
|
| |
|
| |
|