shm: fix comment about wl_shm_buffer_begin_access() safety

The paragraph later says that accessing different buffers is
allowed. The function checks whether the same pool is accessed.

Signed-off-by: Simon Ser <contact@emersion.fr>
This commit is contained in:
Simon Ser 2025-03-15 23:49:43 +01:00
parent d2a3d33063
commit 9dd1b2d7e3

View file

@ -717,7 +717,7 @@ init_sigbus_data_key(void)
* terminate. * terminate.
* *
* It is safe to nest calls to these functions as long as the nested * It is safe to nest calls to these functions as long as the nested
* calls are all accessing the same buffer. The number of calls to * calls are all accessing the same pool. The number of calls to
* wl_shm_buffer_end_access must match the number of calls to * wl_shm_buffer_end_access must match the number of calls to
* wl_shm_buffer_begin_access. These functions are thread-safe and it * wl_shm_buffer_begin_access. These functions are thread-safe and it
* is allowed to simultaneously access different buffers or the same * is allowed to simultaneously access different buffers or the same