From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andries.Brouwer@cwi.nl, Alexander Viro <viro@math.psu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH+discussion] symlink recursion
Date: Wed, 19 Jun 2002 00:12:10 -0700 [thread overview]
Message-ID: <20020619071210.GG25360@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206181646220.2562-100000@penguin.transmeta.com>
On Tue, Jun 18, 2002 at 04:57:06PM -0700, Linus Torvalds wrote:
> I see no advantages to handling it by hand, since this isn't even a very
> deep recursion, and since even if you do the recursive part by hand by a
> linked list you still need to limit the depth _anyway_ to avoid DoS
> attacks.
I see one: the space consumed by the explicitly managed stack is
known and control may be exerted over it. Also, the stack space
consumed by procedure calls is great enough on various non-x86 cpus
to make even shallow recursions problematic (ISTR 96B-120B/call with
a 4KB page in some prior discussions).
Cheers,
Bill
next prev parent reply other threads:[~2002-06-19 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 22:19 [PATCH+discussion] symlink recursion Andries.Brouwer
2002-06-18 23:57 ` Linus Torvalds
2002-06-19 7:12 ` William Lee Irwin III [this message]
2002-06-19 11:48 ` Rogier Wolff
2002-06-19 14:44 ` Daniel Phillips
2002-06-19 16:05 ` Linus Torvalds
2002-06-19 18:18 ` Andries Brouwer
2002-06-19 18:55 ` Linus Torvalds
2002-06-19 19:14 ` David Mosberger
2002-06-19 22:06 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 7:02 Andries.Brouwer
2002-06-19 20:01 Andries.Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020619071210.GG25360@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox