Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115925 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 10815 invoked from network); 3 Sep 2021 12:22:04 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Sep 2021 12:22:04 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id F2B2F1804C8 for ; Fri, 3 Sep 2021 05:58:32 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 3 Sep 2021 05:58:32 -0700 (PDT) Received: by mail-lj1-f176.google.com with SMTP id j12so9462263ljg.10 for ; Fri, 03 Sep 2021 05:58:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fmPrRkXiu01p/n+FP1oDMwHg2rgfjqVVW9eX4xw6sd8=; b=Jtkq5yRRBrNyr93oC7joEhZzAeYMJlqQrev/wrb2j6qpFb+L7jUiRaxW5zfgWfj+HX Du9zQWl192iSQc65CWO1kF/TghA5XqzFd35Wa45cOZwLG8sqRN2x5oPoCGwFqDoHzxuG +IBBT00nTDCPBbxv2ir/2ojvYMLxrQMPGl8SCgzcO3dP6TiAe4/TIS3y6c0udjeY0a4o Lj5CGlEYgMUhzPhB5fzK+2ElYVxPUr02uO1IWlpHba8jqdXLVHcjlWPSoZGHFJhux8D7 PAfPYNBiWBqPs3ekpUU8QLmRkFU0FNCdijgdyUjvAL6OGHFGZs0jUd/jH0ksSTz1y+oS t1hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fmPrRkXiu01p/n+FP1oDMwHg2rgfjqVVW9eX4xw6sd8=; b=oyeDZBf06qqtUJGExC0JuttFf0vf7pqdP8DOaKYAJh/R66lKHWXTpjEj8g8+fTcDIK rGv9h0L7WRIZ9b9MdlO9TqCWXvDix+ukkXdnbVP0aea8RRyAduca1N4hU8HpXxAIEvui B4tDiIo8vjOiRx9qvg1aukjtP8l1tW0mSlNYkD7o0bn0z1nbhfbBQDdEOc06Cz4i6M5V f5xfjAiFFIJ0N3nA/65VFx1WUr2N3Y76/RjdJn34zeVZAeNniGe1bhqT/OPdOBalpQAI B0xgCGbWwZxNxHOM7wElHL7e44VYYsT1l80h/0/hm9QIOXaBtZOs7SmAKeXpYqYMzCxT CeMQ== X-Gm-Message-State: AOAM531SwagPlbO3km3x7vDGKAsJmMaoUW8lYyN/nVQ22QLdoZOGPBCJ LD1AwldGQ5ibnB9v1uHA3vWaF868OdOi9bmiH7xc/Opt X-Google-Smtp-Source: ABdhPJysBvBZa/uQPDWxPKnVaz3d5TrF3XGqnWm1GQFqZZxXxNmGcZYZ//xN8riBjTMV4ZrFFhy/LH309iITCI2KJLY= X-Received: by 2002:a2e:8610:: with SMTP id a16mr2805228lji.33.1630673911303; Fri, 03 Sep 2021 05:58:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 3 Sep 2021 14:58:15 +0200 Message-ID: To: kevin@lyda.ie Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000003a51e605cb16db5f" Subject: Re: [PHP-DEV] Adding a way to disable the stat cache From: nikita.ppv@gmail.com (Nikita Popov) --0000000000003a51e605cb16db5f Content-Type: text/plain; charset="UTF-8" On Thu, Sep 2, 2021 at 10:27 AM Kevin Lyda wrote: > PHP has a stat cache which is... unfortunate. As noted in this bug from > 2004[0] it causes a number of issues for PHP users and is irrelevant > in modern operating systems. Heck, it's not even useful in OS's people > might consider ancient at this point. > > I have a PR[1] to fix this, but had not noticed it had been referred to > this mailing list. I'll need fix the PR at this point as the code has > drifted, but before I do, can whatever discussion happen so that the PR > will be accepted? The change I've made will allow people to disable the > cache so that it won't cause errors and it leaves the current broken > behaviour in place. So there's no real change to the user experience > except they now have a tool to disable buggy behaviour. I feel that > this is the least intrusive way to fix this bug. > > In the discussion on the bug there was resistance to getting rid of the > cache so this was the solution proposed in 2007 and seemed reasonable. > The default behaviour remains but can be turned off by people who want > it off - and there are a number of people who would like it off. > > Is this an acceptable solution? Would this functionality be accepted > either via my PR or another. > > Kevin > > [0]: https://bugs.php.net/bug.php?id=28790 > [1]: https://github.com/php/php-src/pull/5894 > Looks like a reasonable addition to me. Regards, Nikita --0000000000003a51e605cb16db5f--