[lkml]   [2019]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10)
----- On Jun 10, 2019, at 4:43 PM, carlos wrote:

> On 6/6/19 7:57 AM, Florian Weimer wrote:
>> Let me ask the key question again: Does it matter if code observes the
>> rseq area first without kernel support, and then with kernel support?
>> If we don't expect any problems immediately, we do not need to worry
>> much about the constructor ordering right now. I expect that over time,
>> fixing this properly will become easier.
> I just wanted to chime in and say that splitting this into:
> * Ownership (__rseq_handled)
> * Initialization (__rseq_abi)
> Makes sense to me.
> I agree we need an answer to this question of ownership but not yet
> initialized, to owned and initialized.
> I like the idea of having __rseq_handled in

Very good, so I'll implement this approach. Sorry for the delayed
feedback, I am traveling this week.



Mathieu Desnoyers
EfficiOS Inc.

 \ /
  Last update: 2019-06-12 16:00    [W:0.069 / U:7.376 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site