Re: Looking at "int vforked" in signal handler is racy

On 11/08/2025 06:00, Herbert Xu wrote:
> On Sun, Aug 10, 2025 at 11:20:40PM +0100, Harald van Dijk wrote:
>>
>> That approach seems solid to me at a very quick glance. I think you don't
>> even need separate have_vfork_sibling and vfork_parent_pid variables, just
>> make the existing vforked variable a pid, or 0. A mostly untested patch
>> using that:
> 
> Looks good to me.  Could you turn this into a patch please? If
> you could run some quick speed tests on this versus the existing
> code that would be even better :)

It will be a little while before I can do meaningful measurements, but I 
will do so when I can.

Cheers,
Harald van Dijk