From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Hinds <dhinds@sonic.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Worst recursion in the kernel
Date: Thu, 4 Dec 2003 14:47:33 +0100 [thread overview]
Message-ID: <20031204134733.GA7890@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20031203150804.A19286@sonic.net>
On Wed, 3 December 2003 15:08:04 -0800, David Hinds wrote:
>
> The issue is that validate_mem() doesn't need to use read_cis_mem's
> functionality directly (so it can't just be modified to use the __*
> form). It calls other stuff, which calls other stuff, which
> eventually calls read_cis_mem(), and all that other stuff is used by
> other callers. So there isn't an obvious place to insert this
> bifurcation.
This explanation sounds a bit like "that mess is too fragile, there is
no way to touch it without everything falling apart." Just one more
reason to change it and make it more maintainable. I agree, it is a
big piece of work waiting for 2.7 to open up, but your only excuse not
to do it eventually is lack of time. ;)
> inv_probe() is pretty comprehensible, it calls itself directly, in
> order to traverse a short linked list from tail to head.
Sounds like a valid candidate for <list.h>, but if you can prove the
list to always be short, it is ok.
Jörn
--
Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface.
-- Doug MacIlroy
prev parent reply other threads:[~2003-12-04 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 14:31 Jörn Engel
2003-12-03 18:07 ` David Hinds
2003-12-03 19:04 ` Jörn Engel
2003-12-03 22:57 ` Russell King
2003-12-03 23:08 ` Mike Fedyk
2003-12-03 23:36 ` David Hinds
2003-12-04 14:14 ` Jörn Engel
2003-12-04 15:08 ` Martin Waitz
2003-12-04 18:40 ` Russell King
2003-12-04 18:46 ` Jörn Engel
2003-12-03 23:08 ` David Hinds
2003-12-04 13:47 ` Jörn Engel [this message]
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=20031204134733.GA7890@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®