Re: Change signal mask after vfork/clone system call

[Alan Cox]

On Thu, 4 Nov 2010 15:37:05 +0000
Gregory Giguashvili <Gregory.Giguashvili@xxxxxxxx> wrote:

> > Fork on pretty much any Unix like system around today does copy-on-write
> >so while not as efficient as vfork should be fine for most purposes.
> Yes, but the problem is that fork simply does not work when a process has huge resident size and vm.overcommit_memory=0 as preferred by Linux distributions we run on. So, processes with large RSS footprint may occasionally fail fork, even if a tiny process is to be started.
> 
> Using vfork always works, but has the signal mask problem. Catch 22?

And is there a reason you can't mask the signals, vfork and unmask them
again after the parent continues ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/