From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: netfilter-devel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 10875] Oops in nf_nat_setup_info
Date: Sat, 07 Jun 2008 14:05:32 +0200 [thread overview]
Message-ID: <484A798C.6000608@trash.net> (raw)
In-Reply-To: <484A788C.3000205@trash.net>
Patrick McHardy wrote:
> Krzysztof Oledzki wrote:
>>
>>
>> On Fri, 6 Jun 2008, Krzysztof Oledzki wrote:
>>
>>> Hello,
>>>
>>> Today I have been plaing with the conntrackd utility and noticed it
>>> is very easy to trigger a kernel oops just by:
>>>
>>> conntrackd -d
>>> conntrackd -n
>>> conntrackd -c
>>> conntrackd -c
>>
>> OK, quite often is is enough to run only the first "conntrackd -c" to
>> crash the kernel.
>
> Is that with or without your accounting patch?
In case its not, does that kernel include commit 86577c661?
next prev parent reply other threads:[~2008-06-07 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 18:05 [Bug 10875] Oops in nf_nat_setup_info Krzysztof Oledzki
2008-06-06 22:47 ` Krzysztof Oledzki
2008-06-07 12:01 ` Patrick McHardy
2008-06-07 12:05 ` Patrick McHardy [this message]
2008-06-07 13:51 ` Krzysztof Oledzki
2008-06-07 13:54 ` Patrick McHardy
2008-06-07 14:58 ` Krzysztof Oledzki
2008-06-07 15:27 ` Patrick McHardy
2008-06-07 15:34 ` Krzysztof Oledzki
2008-06-07 13:27 ` 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=484A798C.6000608@trash.net \
--to=kaber@trash.net \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@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.