Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67774
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.223.169 cause and error)
References: <CAAyV7nEx32ni3J0dOQprJCXd=4D06XwS0-Ro811OtqmPeEyYJg@mail.gmail.com>
 <CABBJUpcz3g6sWZR_K+p6fe0_nP7YZqW1XgZ54ktgA1KgD6xchg@mail.gmail.com>
 <CAAyV7nGFnDOzfR9B8PfgnbbG70ZVdwzx0XfZak9LoKuTSOkvEQ@mail.gmail.com>
 <51C38014.4090906@sugarcrm.com> <CAAyV7nGM5=e9bP7CtTjbUcnyk1m_C+MSDSEN5zYSbvt59wTSNQ@mail.gmail.com>
 <51C3C673.5060408@sugarcrm.com>
In-Reply-To: <51C3C673.5060408@sugarcrm.com>
MIME-Version: 1.0
Thread-Index: AQHp9GqsamRfrNXp8kZv4cd0qFOBGAJAleB2AWPDl+MB90sMrQEnL9Y+AfaRmEuYxC+ZkA==
Date: Fri, 21 Jun 2013 19:41:22 -0700
Message-ID: <135ff3b963c3c90cd0e3ab1a69a1c37f@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>, Anthony Ferrara <ircmaxell@gmail.com>
Cc: Laruence <laruence@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: RE: [PHP-DEV] Disabling the GC during shutdown
From: andi@zend.com (Andi Gutmans)

>-----Original Message-----
>From: Stas Malyshev [mailto:smalyshev@sugarcrm.com]
>Sent: Thursday, June 20, 2013 8:20 PM
>To: Anthony Ferrara
>Cc: Laruence; internals@lists.php.net
>Subject: Re: [PHP-DEV] Disabling the GC during shutdown
>
>> However, that's not really fixing the situation either, as the zval is
>> still getting nuked (but only partially).
>
>If there's a memory overwrite or use-after-free is going on, this patch
is not a
>complete solution - it relies on the fact that "bad" data will be always
out of
>range of "good" data. I see no way to ensure that - so if there's an
overwrite
>that writes garbage inside the object there will be situations where the
>garbage looks exactly like a valid object ID and it will still crash, but
it would
>be significantly harder to reproduce.
>So I think before patching it we need to get to the root cause and figure
out
>why it happens and what causes it, instead of partially fixing the
symptom

I agree with that. I think it'd be a mistake to submit any patch without
us understanding root cause.
We may cover up a bug which will resurface elsewhere...
Hopefully you can find a way to pin it down.

Thanks for putting this much effort into it!
Andi