Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67779 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11981 invoked from network); 22 Jun 2013 11:57:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jun 2013 11:57:20 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.48 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.215.48 mail-la0-f48.google.com Received: from [209.85.215.48] ([209.85.215.48:34890] helo=mail-la0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/C1-01790-C1195C15 for ; Sat, 22 Jun 2013 07:57:17 -0400 Received: by mail-la0-f48.google.com with SMTP id lx15so8301597lab.7 for ; Sat, 22 Jun 2013 04:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=kJ4UGyYbQMelzO66HbRX11azoR5xTUbODXNgNJN1xaw=; b=Bkm41JOawFaxFvnCel6frOIWXOqExWgwNPQ5UDZL7yxaIiPO3NQDQbumXqSklP/cyZ P2v0Ve1U62w4dUnIIGUgBlrvFNT8CZZK5qgo9MgmbyfhqvH4Pr8DmVI8RDBwFLSlydyj 3HJ3YJQPIvMcF0LgaRTRMdS2Mf7N5daUal16/sPM6dSjlJa7XUCSmgfgd/P8RmosFvqj qL57w31ImbDE/5Q/jqV0Z6V6q0Wocmg8/PITD8XRwmLgWTekOlK6A0uIE++QETQqTFvU RDSaWYAUizdhqH3Qw7co7EXXh7/HsYpWImHEEMGAoHDVldqTIBDzBrmorji0J1vcK7gU 9amA== X-Received: by 10.112.211.167 with SMTP id nd7mr9401589lbc.59.1371902233704; Sat, 22 Jun 2013 04:57:13 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.114.29.36 with HTTP; Sat, 22 Jun 2013 04:56:53 -0700 (PDT) In-Reply-To: References: <51C38014.4090906@sugarcrm.com> <51C3C673.5060408@sugarcrm.com> <135ff3b963c3c90cd0e3ab1a69a1c37f@mail.gmail.com> Date: Sat, 22 Jun 2013 19:56:53 +0800 X-Google-Sender-Auth: 1IvkaT1mDUjsyzBOJLq9DBhhSf8 Message-ID: To: Arnaud Le Blanc Cc: Andi Gutmans , Stas Malyshev , Anthony Ferrara , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Disabling the GC during shutdown From: laruence@php.net (Laruence) On Sat, Jun 22, 2013 at 6:06 PM, Arnaud Le Blanc wrote: > Hi, > > This bug may be related (and has a reproducing script) : > https://bugs.php.net/bug.php?id=63734 > Hey: I probably has fixed this bug(actually, according to the reporter this bug is due to Opcache): according to the latest feedback from the reporter: https://github.com/zendtech/ZendOptimizerPlus/issues/95#issuecomment-19854473 "Incredible, but it works ! Tested ZendOptimizerPlus latest version (ba6c5f3) : segfault Applied your patch : fully works" so, I think this bug is probable like the previous one we already fixed: https://github.com/php/php-src/commit/e88cdaa0 thanks > > On Sat, Jun 22, 2013 at 4:41 AM, Andi Gutmans wrote: >> >> >-----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 >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > -- Laruence Xinchen Hui http://www.laruence.com/