Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51290
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Antony Dovgal <tony@daylessday.org>
Cc: php-dev <internals@lists.php.net>
In-Reply-To: <4D305A91.8020806@daylessday.org>
References: <4D305A91.8020806@daylessday.org>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 17 Jan 2011 19:19:27 +0100
Message-ID: <1295288368.3927.26.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] fully enabling dl() for FPM SAPI
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2011-01-14 at 17:15 +0300, Antony Dovgal wrote:
> Hi all!
> 
> Are there any objections if I disable E_DEPRECATED notice in dl() for FPM SAPI?
> The notice is already disabled for CGI/FastCGI, CLI and Embed SAPIs.
> I believe there's no reason for this notice in case of FPM, too.
> 
> Patch: http://dev.daylessday.org/diff/fpm_dl_notice.diff

I think it can be quite dangerous if you have extensions living shorter
than the PHP process. Not only might dlclose() cause some leaks but
there are a few extensions playing with function pointers or opcode
handlers which aren't properly reset so a following request might try to
jump to invalid memory.

Additionally there's no restriction on this once safe_mode is gone, so
anybody could load any C extension - while that can be fixed by
advertising disable_function=dl


johannes