Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57299 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57046 invoked from network); 9 Jan 2012 16:50:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jan 2012 16:50: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.212.42 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:61296] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D6/52-46289-BCA1B0F4 for ; Mon, 09 Jan 2012 11:50:20 -0500 Received: by vbbfd1 with SMTP id fd1so2923568vbb.29 for ; Mon, 09 Jan 2012 08:50:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=ZsJAh+piw9POeF+iVzONHbR79MMWCTG3N4H1DAI6U0M=; b=JgcXgiIuzZzTiyyxLdIBoE3G0dsgMjalSjJhIB4+3DLHCxiNFU4XIRA1JPEHaRjA8v 96FemscI85qD430L1WqJHLUPzN+7EOQJwWNcsLFyjluufZJJgs+Ye6hgULn/XFJxAz8V Y/VysbcPX3P3/WOca25f6+S1JJK11k7pWmHPQ= Received: by 10.52.33.68 with SMTP id p4mr7895763vdi.52.1326127816195; Mon, 09 Jan 2012 08:50:16 -0800 (PST) References: <6268389813742875794@unknownmsgid> In-Reply-To: Mime-Version: 1.0 (1.0) Date: Tue, 10 Jan 2012 00:50:11 +0800 Message-ID: <6614496271356606712@unknownmsgid> To: Stefan Esser Cc: Pierre Joye , PHP internals , =?UTF-8?Q?Johannes_Schl=C3=BCter?= , Laruence Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: 5.3.9, Hash DoS, release From: laruence@gmail.com (Xinchen Hui) Hi: I am not sure whether you have understood my point. If an array have more than 1024 buckets in an same bucket list(same index), there must already be an performance issue. Sent from my iPhone =E5=9C=A8 2012-1-10=EF=BC=8C0:41=EF=BC=8CStefan Esser = =E5=86=99=E9=81=93=EF=BC=9A > Hey, > >> That is Restricting a max length of a buckets list in a hash table. >> >> If a bucket's length exceed 1024, any insertion into this bucket >> will return failure and a warning will be generated. >> >> What do you think? > > very bad idea. Especially when it comes to numerical indices a legitimate= application might put data into a big array and have legitimate colliding = keys. > > Regards, > Stefan Esser