Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57309
Return-Path: <laruence@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 73422 invoked from network); 9 Jan 2012 17:22:17 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 9 Jan 2012 17:22:17 -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:34474] helo=mail-vw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F3/16-46289-8422B0F4 for <internals@lists.php.net>; Mon, 09 Jan 2012 12:22:16 -0500
Received: by vbbfd1 with SMTP id fd1so2954316vbb.29
        for <internals@lists.php.net>; Mon, 09 Jan 2012 09:22:13 -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=44HZN0j0WDElpUEQgK+qRIe4FFrGLF66vGz1fGI6DJA=;
        b=hkm0KLEa6VZyfL7Fylm4M7pQKlDd0oROlPwx+oRyTb5wEJYby5HZUAYKWJ2nrAsK3C
         1kHCJL4TGabcAkpKVvm5ZL2UHAlP+qSTEEdkFgAVaSvtf+GCQY/hzG8WtJf4B/amOKA7
         ecDuz+2/BBmaxXXHiVrfG8Q1nr/n2TgoeYstY=
Received: by 10.52.33.68 with SMTP id p4mr7967352vdi.52.1326129733814; Mon, 09
 Jan 2012 09:22:13 -0800 (PST)
References: <CAEZPtU44aag3z-oGAx+mF1dvr9qF0ZLpdW3pHFWEe0uwbchMBQ@mail.gmail.com>
 <6268389813742875794@unknownmsgid> <BB121D7B-95AC-4DBB-9D39-5337138AFC77@nopiracy.de>
 <6614496271356606712@unknownmsgid> <4F0B2091.7080301@php.net> <2146847516644307992@unknownmsgid>
In-Reply-To: <2146847516644307992@unknownmsgid>
Mime-Version: 1.0 (1.0)
Date: Tue, 10 Jan 2012 01:22:10 +0800
Message-ID: <-3716286819925347549@unknownmsgid>
To: Xinchen Hui <laruence@gmail.com>
Cc: Rasmus Lerdorf <rasmus@php.net>, Stefan Esser <stefan@nopiracy.de>, 
	Pierre Joye <pierre.php@gmail.com>, PHP internals <internals@lists.php.net>, 
	=?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	Laruence <laruence@php.net>
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)

Sent from my iPhone

=E5=9C=A8 2012-1-10=EF=BC=8C1:18=EF=BC=8CXinchen Hui <laruence@gmail.com> =
=E5=86=99=E9=81=93=EF=BC=9A

> Sent from my iPhone
>
> =E5=9C=A8 2012-1-10=EF=BC=8C1:14=EF=BC=8CRasmus Lerdorf <rasmus@php.net> =
=E5=86=99=E9=81=93=EF=BC=9A
>
>> On 01/09/2012 08:50 AM, Xinchen Hui wrote:
>>> 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.
>>
>> The problem is you really need to consider the source. There are many
>> places where people deal with huge datasets. If they assign it directly
>> they shouldn't hit any limits or we would need some sort of "large
>> array" hint which would be nasty.
> Rasmus:
>
> Large array ! =3D Large list
>
> An array can have million elements withou exceed the limit ion of max
> length of list.
>
> Thanks

And sorry I can not do it now ,since it's really later here now and I
have getup early tomorrow to work.

So anyone who have time can try to implement it, just remember also do
limit in resize hash logic.

Thanks very much.
>>
>> -Rasmus