mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gregory Giguashvili <Gregory.Giguashvili@PDGM.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Change signal mask after vfork/clone system call
Date: Thu, 4 Nov 2010 15:45:43 +0000	[thread overview]
Message-ID: <20101104154543.2a71cff1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <DAF636D3923A51488784A1F985996EE804206DDF@exil1.paradigmgeo.net>

On Thu, 4 Nov 2010 15:37:05 +0000
Gregory Giguashvili <Gregory.Giguashvili@PDGM.com> 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 ?

  reply	other threads:[~2010-11-04 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  7:53 Gregory Giguashvili
2010-10-20  7:56 ` Gregory Giguashvili
2010-11-04  6:08 ` Gregory Giguashvili
2010-11-04  9:48   ` Alan Cox
2010-11-04 15:37     ` Gregory Giguashvili
2010-11-04 15:45       ` Alan Cox [this message]
2010-11-04 16:20         ` Gregory Giguashvili
2010-11-04 16:28           ` Alan Cox
2010-11-04 16:43             ` Gregory Giguashvili
2010-11-05  7:32     ` Gregory Giguashvili

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101104154543.2a71cff1@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Gregory.Giguashvili@PDGM.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®