Christian Schwarz 2bc2fd9cfd fixup(#7160 / tokio_epoll_uring_ext): double-panic caused by info! in thread-local's drop() (#7164) ...

Manual testing of the changes in #7160 revealed that, if the
thread-local destructor ever runs (it apparently doesn't in our test
suite runs, otherwise #7160 would not have auto-merged), we can
encounter an `abort()` due to a double-panic in the tracing code.

This github comment here contains the stack trace:
https://github.com/neondatabase/neon/pull/7160#issuecomment-2003778176

This PR reverts #7160 and uses a atomic counter to identify the
thread-local in log messages, instead of the memory address of the
thread local, which may be re-used.

2024-03-18 16:12:01 +01:00

..

io_engine

fixup(#7160 / tokio_epoll_uring_ext): double-panic caused by info! in thread-local's drop() (#7164)

2024-03-18 16:12:01 +01:00

owned_buffers_io

tokio-epoll-uring: use it for on-demand downloads (#6992)

2024-03-15 18:57:05 +00:00

io_engine.rs

build: make procfs linux only dependency (#7156)

2024-03-18 09:28:45 +00:00

metadata.rs

tokio-epoll-uring: use it on the layer-creating code paths (#6378)

2024-03-05 09:03:54 +00:00

open_options.rs

tokio-epoll-uring: retry on launch failures due to locked memory (#7141)

2024-03-15 19:46:15 +00:00