On Thu, Nov 22, 2018 at 01:35:44PM -0500, Mathieu Desnoyers wrote: > ----- On Nov 22, 2018, at 11:24 AM, Szabolcs Nagy Szabolcs.Nagy@xxxxxxx wrote: > > > On 22/11/18 15:33, Mathieu Desnoyers wrote: > >> ----- On Nov 22, 2018, at 10:21 AM, Florian Weimer fweimer@xxxxxxxxxx wrote: > >>> Right, but in case of user-supplied stacks, we actually free TLS memory > >>> at this point, so signals need to be blocked because the TCB is > >>> (partially) gone after that. > >> > >> Unfortuntately, disabling signals is not enough. > >> > >> With rseq registered, the kernel accesses the rseq TLS area when returning to > >> user-space after _preemption_ of user-space, which can be triggered at any > >> point by an interrupt or a fault, even if signals are blocked. > >> > >> So if there are cases where the TLS memory is freed while the thread is still > >> running, we _need_ to explicitly unregister rseq beforehand. > > > > i think the man page should point this out. > > Yes, I should add this to the proposed rseq(2) man page. > > > > > the memory of a registered rseq object must not be freed > > before thread exit. (either unregister it or free later) > > > > and ideally also point out that c language thread storage > > duration does not provide this guarantee: it may be freed > > by the implementation before thread exit (which is currently > > not observable, but with the rseq syscall it is). > > How about the following wording ? > > Memory of a registered rseq object must not be freed before the > thread exits. Reclaim of rseq object's memory must only be > done after either an explicit rseq unregistration is performed > or after the thread exit. Keep in mind that the implementation > of the Thread-Local Storage (C language __thread) lifetime does > not guarantee existence of the TLS area up until the thread exits. This is all really ugly for application/library code to have to deal with. Maybe if the man page is considered as documenting the syscall only, and not something you can use, it's okay, but "until the thread exits" is not well-defined in the sense you want it here. It's more like "until the kernel task for the thread exits", and the whole point is that there is some interval in time between the abstract thread exit and the kernel task exit that is not observable without rseq but is observable if the rseq is wrongly left installed. Rich
