From: Nuno Ferreira <nuno.ferreira@graycell.biz>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: akpm@osdl.org, Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: 2.6.9-rc2-mm2 fn_hash_insert oops
Date: Thu, 23 Sep 2004 22:38:04 +0100 [thread overview]
Message-ID: <1095975485.4339.1.camel@taz.graycell.biz> (raw)
In-Reply-To: <E1CARaS-00071j-00@gondolin.me.apana.org.au>
On Qui, 2004-09-23 at 21:16 +1000, Herbert Xu wrote:
> Lukas Hejtmanek <xhejtman@mail.muni.cz> wrote:
> >
> > However there is still the issue with endless loop in fn_hash_delete :(
>
> Same problem, same fix. Can someone think of a generic fix to
> list_for_each_*?
>
This also fixed the problem I reported earlier with the machine freezing
when my Speedtouch USB ADSL modem connected.
Thanks
prev parent reply other threads:[~2004-09-23 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040923103723.GA12145@mail.muni.cz>
2004-09-23 11:16 ` 2.6.9-rc2-mm2 fn_hash_insert oops Herbert Xu
2004-09-23 14:02 ` Lukas Hejtmanek
2004-09-23 19:18 ` Ingo Molnar
2004-09-23 20:36 ` David S. Miller
2004-09-23 23:29 ` Martin Diehl
2004-09-23 21:38 ` Nuno Ferreira [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=1095975485.4339.1.camel@taz.graycell.biz \
--to=nuno.ferreira@graycell.biz \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).