From: Patrick McHardy <kaber@trash.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
coreteam@netfilter.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [netfilter-core] Re: [lockup] 2.6.17-rc3: netfilter/sctp: lockup in sctp_new(), do_basic_checks()
Date: Tue, 02 May 2006 17:55:30 +0200 [thread overview]
Message-ID: <445780F2.8080102@trash.net> (raw)
In-Reply-To: <1146584081.19488.57.camel@localhost>
Marcel Holtmann wrote:
> Hi Ingo,
>
>
>>running an "isic" stresstest on and against a testbox [which, amongst
>>other things, generates random incoming and outgoing packets] on
>>2.6.17-rc3 (and 2.6.17-rc3-mm1) over gigabit results in a reproducible
>>lockup, after 5-10 minutes of runtime:
>
>
> does this lockup the local machine you run the stresstest on or the
> remote machine you run the test against?
It would lock up any machine with the SCTP conntrack module loaded.
I'll prepare a patch for -stable as well.
prev parent reply other threads:[~2006-05-02 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 11:34 [lockup] 2.6.17-rc3: netfilter/sctp: lockup in sctp_new(), do_basic_checks() Ingo Molnar
2006-05-02 13:40 ` Ingo Molnar
2006-05-02 13:45 ` Ingo Molnar
2006-05-02 13:54 ` [netfilter-core] " Patrick McHardy
2006-05-02 14:01 ` Ingo Molnar
2006-05-02 13:57 ` Patrick McHardy
2006-05-02 14:16 ` Ingo Molnar
2006-05-02 14:24 ` Ingo Molnar
2006-05-02 14:29 ` Patrick McHardy
2006-05-02 14:38 ` Ingo Molnar
2006-05-02 14:35 ` Patrick McHardy
2006-05-02 14:42 ` Ingo Molnar
2006-05-02 14:40 ` Patrick McHardy
2006-05-02 13:45 ` [netfilter-core] " Patrick McHardy
2006-05-02 15:34 ` Marcel Holtmann
2006-05-02 15:55 ` Patrick McHardy [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=445780F2.8080102@trash.net \
--to=kaber@trash.net \
--cc=akpm@osdl.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@elte.hu \
/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