diff options
| author |  Abseil Team <absl-team@google.com> | 2023-11-14 13:38:32 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-worker@google.com> | 2023-11-14 13:39:13 -0800 |
| commit | 67f3af264c5b32cb92bb72440220e03591128f40 (patch) | |
| tree | 3609b9991d367d4a224976bf86629a37256d3304 /absl/base/internal | |
| parent | 1415840502f38952e63c1c6e4892f6e69ce7bc13 (diff) | |
Fix documentation on when SpinLock is async-signal-safe
PiperOrigin-RevId: 582426024
Change-Id: Ic8650de4faff9688f4cb5529c1df9bc752878b5a
Diffstat (limited to 'absl/base/internal')
| -rw-r--r-- | absl/base/internal/spinlock.h | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/absl/base/internal/spinlock.h b/absl/base/internal/spinlock.h index 6818a86a..2929cd6f 100644 --- a/absl/base/internal/spinlock.h +++ b/absl/base/internal/spinlock.h @@ -19,10 +19,10 @@ // - for use by Abseil internal code that Mutex itself depends on // - for async signal safety (see below) -// SpinLock is async signal safe. If a spinlock is used within a signal -// handler, all code that acquires the lock must ensure that the signal cannot -// arrive while they are holding the lock. Typically, this is done by blocking -// the signal. +// SpinLock with a base_internal::SchedulingMode::SCHEDULE_KERNEL_ONLY is async +// signal safe. If a spinlock is used within a signal handler, all code that +// acquires the lock must ensure that the signal cannot arrive while they are +// holding the lock. Typically, this is done by blocking the signal. // // Threads waiting on a SpinLock may be woken in an arbitrary order. |