[PATCH] malloc: Fix [BZ #22853] weak randomization on thread arenas.

[iripoll]

Hello,

   Our aim is to sing the copyright assignment ASAP. But please, give us some time to check it with 
our respective universities.

  It may take longer than normal because of the covid-19. We are under full lockdown.

Best,
Ismael.


El 25/3/20 a las 21:05, Carlos O'Donell escribió:
> On 3/25/20 10:56 AM, iripoll wrote:
>> Hello,
>>
>>>>
>>>
>>> Alright, could you post a v2 with the inline functions change, without
>>> the test and with a proper commit message?
>>>
>>> Thanks for you patience and for the work on moving this forward.
>>>
>>
>> Here is the the patch with all the comments and suggestions.
> 
> I am excited that this kind of work is going forward.
> 
> The next step here is that we need to work out the copyright assignment
> for this work so we can accept the patches.
> 
> The contribution checklist explains "FSF copyright Assignment":
> https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment
> 
> I would suggest a futures assignment:
> http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
> 
> This would allow the community to review and accept any of your
> patches that you post
> 
> If you're going through the process I usually recommend getting
> assignments in place for glibc, gcc, gdb, and binutils, because
> all 4 projects share headers, that way you can post patches
> across all of them. However, this is just a recommendation.
> 
> If your educational institution claims copyright on work you
> create you may need to tell the FSF that and they in turn may
> need to sign a corporate disclaimer.
> 
> This process is usually quite fast and smooth.
> 
> Your last patches in 2013 were < 15 lines, and so were accepted
> under the flexible rules regarding legally significant
> contributions.
> 
> Thank you again for all of this work! :-)
> 
> Cheers,
> Carlos.
>