[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101104162828.7862a49d@lxorguk.ukuu.org.uk>
Date: Thu, 4 Nov 2010 16:28:28 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Gregory Giguashvili <Gregory.Giguashvili@...M.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Change signal mask after vfork/clone system call
> Now, I could unmask signals for the thread calling vfork, but it seems not a signal-safe solution to me because signals may arrive to this thread until I reestablish the mask. pthread_atfork call comes to rescue to address such issues for fork, but there seems to be nothing for vfork call.
Oh you are wrapping buggy apps ?
vfork
exec a tiny app which fixes the signals and execs the proper app
or fix the apps being run...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists