Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84596
Return-Path: <smalyshev@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 43576 invoked from network); 11 Mar 2015 22:46:54 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 11 Mar 2015 22:46:54 -0000
Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender)
X-PHP-List-Original-Sender: smalyshev@gmail.com
X-Host-Fingerprint: 209.85.192.169 mail-pd0-f169.google.com  
Received: from [209.85.192.169] ([209.85.192.169:46091] helo=mail-pd0-f169.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 5D/F8-32765-CD5C0055 for <internals@lists.php.net>; Wed, 11 Mar 2015 17:46:54 -0500
Received: by pdev10 with SMTP id v10so14612378pde.13
        for <internals@lists.php.net>; Wed, 11 Mar 2015 15:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=9c/HnII7w+qkCnmYI9Lnl4833snGXymsy87kGDaoMyw=;
        b=iRpMsnQ1+2JNCXX38d+nSrO6blomei3doHsw70qSAMHf/PNgsXzXkHVvHGrKjENn4a
         D3mnMdH8bGuEW9kW8a7VL6pyp5m4e74PxspBFqLWuPjX0semjYvnkRId/Y88evdcqMgi
         ypAREMfWpUeIZaDnxYoJaGwq01E1C+2gyOxiMLfUbPKTjfE1OVOnd0N0mpboyfFwvxxE
         9kffwuogyu9BYHEAXng/CSHpNf8Z618SmiX9r1aloesQSFvu2iKTiCMIYEQIuClMtzxo
         w0Qe0FkqSRXUKzwQhDyHbUR0JAQTiVUntWLshPLqxgcmSrv8RlqBk57wmLMsNsV0AMNV
         o4pA==
X-Received: by 10.70.37.134 with SMTP id y6mr84050439pdj.13.1426114009351;
        Wed, 11 Mar 2015 15:46:49 -0700 (PDT)
Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48])
        by mx.google.com with ESMTPSA id c9sm7771483pdo.13.2015.03.11.15.46.47
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 11 Mar 2015 15:46:48 -0700 (PDT)
Message-ID: <5500C5D7.9010808@gmail.com>
Date: Wed, 11 Mar 2015 15:46:47 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Dmitry Stogov <dmitry@zend.com>
CC: Rasmus Lerdorf <rasmus@lerdorf.com>, 
 Nikita Popov <nikita.ppv@gmail.com>,
 Xinchen Hui <xinchen.h@zend.com>, Anatol Belski <ab@php.net>, 
 PHP Internals <internals@lists.php.net>
References: <CA+9eiLs9rd8bcQzoOQ8t465FYOfZvw2_HW=XS7OeofO+_qkOCg@mail.gmail.com>	<5500C04D.9000805@gmail.com> <CA+9eiLtszcUBaDbKHY_g5M8rM41w_+vhn7pZsaW0EuyHB9PBcw@mail.gmail.com>
In-Reply-To: <CA+9eiLtszcUBaDbKHY_g5M8rM41w_+vhn7pZsaW0EuyHB9PBcw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Safe execution timeout handling
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I think, after "max_execution_time" is exceeded, we may start another
> "hard_timeout", and in case the EG(vm_interrupt) wasn't handled
> "safely", kill the process.

I remember such proposal floating on the list recently, with two-stage
timeouts. But wouldn't killing the process run the same risk that it
left something messed up in SHM?

Also, in threaded environments that's probably not an option, and PHP
may not even own the thread.

-- 
Stas Malyshev
smalyshev@gmail.com