All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Krzysztof Oledzki <olenf@ans.pl>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: kernel BUG at kernel/sched.c:2833!
Date: Mon, 21 Nov 2005 15:46:39 +0100	[thread overview]
Message-ID: <4381DDCF.7090609@eurodev.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511211541020.30476@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
>> I can't reproduce that problem that you're reporting. I don't see how
>> the ctnetlink code can trigger that at the moment :(
> 
> What information should I provide to help tracking this bug?

Any extra patch applied to your vanilla kernel? architecture? whatever
that can give me a clue on what's wrong. Send me such info in private if
you want.

>> The only bugfix that was in my pending queue is:
>> [PATCH] relax ip_conntrack_[nat_]proto_find_get checkings
> 
> OK. I'll test this patch.

Fine.

-- 
Pablo

  reply	other threads:[~2005-11-21 14:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14  9:50 kernel BUG at kernel/sched.c:2833! Krzysztof Oledzki
2005-11-14 12:27 ` Pablo Neira
2005-11-16 21:16   ` Krzysztof Oledzki
2005-11-17  0:36     ` Pablo Neira
2005-11-17 15:11       ` Harald Welte
2005-11-18  3:19         ` Pablo Neira
2005-11-18  3:25           ` Pablo Neira
2005-11-21  9:48             ` Krzysztof Oledzki
2005-11-18  8:37           ` Harald Welte
2005-11-17 22:04       ` Krzysztof Oledzki
2005-11-21 14:24         ` Pablo Neira
2005-11-21 14:42           ` Krzysztof Oledzki
2005-11-21 14:46             ` Pablo Neira [this message]
2005-11-21 17:05               ` Patrick McHardy
2005-11-21 21:20               ` Krzysztof Oledzki
2005-11-25  2:52                 ` Pablo Neira Ayuso
2005-11-25 11:43                   ` Krzysztof Oledzki
2005-11-22 11:40           ` Krzysztof Oledzki

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=4381DDCF.7090609@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=olenf@ans.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.