From: m0sia <m0sia@plotinka.ru>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11571] New: u32_classify Kernel Panic
Date: Thu, 18 Sep 2008 13:05:28 +0600 [thread overview]
Message-ID: <48D1FDB8.4040805@plotinka.ru> (raw)
In-Reply-To: <20080917193832.GA2623@ami.dom.local>
Jarek Poplawski пишет:
> Andrew Morton wrote, On 09/16/2008 06:15 PM:
>
>
>> (switched to email. Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).
>>
>> On Mon, 15 Sep 2008 03:35:16 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>>
>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=11571
>>>
>>> Summary: u32_classify Kernel Panic
>>>
> ...
>
> Could you add more details:
> - .config
> - gzipped cls_u32.o (compiled with CONFIG_DEBUG_INFO on)
> - the first part of OOPS if possible.
> - more exactly these tc commands from your script
>
> Does this happen while creating or deleting something and is this
> easy to reproduce?
>
> Thanks,
> Jarek P.
>
It happens on a production server and i can't experiment with this bug.
Now i'm using MARK iptable target and fw mark filter, because of this
bug. I think it happens when deleting or adding filters(it occur
automatically by script, when adding new user or user change speed).
I'll try this patch on test server.
next prev parent reply other threads:[~2008-09-18 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11571-10286@http.bugzilla.kernel.org/>
2008-09-16 16:15 ` [Bugme-new] [Bug 11571] New: u32_classify Kernel Panic Andrew Morton
2008-09-17 19:38 ` Jarek Poplawski
2008-09-17 22:08 ` Jarek Poplawski
2008-09-18 7:05 ` m0sia [this message]
2008-09-18 7:53 ` Jarek Poplawski
2009-01-05 13:52 ` [PATCH] " Jarek Poplawski
2009-01-06 2:14 ` David Miller
2008-10-11 11:17 ` pkt_sched: cls_u32: Fix locking in u32_delete() Jarek Poplawski
2008-10-11 14:10 ` Herbert Xu
2008-10-11 19:24 ` David Miller
2008-10-11 22:04 ` Jarek Poplawski
2008-10-11 22:05 ` David Miller
2008-10-13 6:46 ` Jarek Poplawski
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=48D1FDB8.4040805@plotinka.ru \
--to=m0sia@plotinka.ru \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jarkao2@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).