From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Eric Dumazet <dada1@cosmosbay.com>, netdev@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at virtual address 000000b0
Date: Thu, 18 Oct 2007 13:46:06 +0200 [thread overview]
Message-ID: <4717477E.8000003@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0710181320170.12701@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
>> Hum, you are using IPT_TPROXY thing, which is not in linux-2.6.22.9
>
> It is only compiled in, not used at the moment.
But at least the previous version (before those patches posted a week
ago) touches the routing code in exactly that function.
next prev parent reply other threads:[~2007-10-18 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 6:40 BUG: unable to handle kernel NULL pointer dereference at virtual address 000000b0 Krzysztof Oledzki
2007-10-17 6:57 ` Eric Dumazet
2007-10-17 8:21 ` Krzysztof Oledzki
2007-10-17 10:38 ` Eric Dumazet
2007-10-17 10:53 ` Krzysztof Oledzki
2007-10-17 13:54 ` Eric Dumazet
2007-10-18 11:22 ` Krzysztof Oledzki
2007-10-18 11:46 ` Patrick McHardy [this message]
2007-10-18 13:15 ` 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=4717477E.8000003@trash.net \
--to=kaber@trash.net \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=olel@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 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).