From: Rolf Fokkens <fokkensr@linux06.vertis.nl>
To: Martin Josefsson <gandalf@marcelothewonderpenguin.com>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.samba.org
Subject: Re: [BUG] vanilla 2.4.15 iptables/REDIRECT kernel oops
Date: Tue, 27 Nov 2001 23:55:53 -0800 [thread overview]
Message-ID: <01112723555300.01996@home01> (raw)
In-Reply-To: <Pine.LNX.4.21.0111271600420.23169-100000@tux.rsn.bth.se>
In-Reply-To: <Pine.LNX.4.21.0111271600420.23169-100000@tux.rsn.bth.se>
OK. So there hasn't been much response for this BUG report. So I did a little
investigating myself.
By use of objdump I get the impression that the Oops shows up when
ip_dont_fragment is called (expanded). To be more specific: sk seems to be
NULL.
This is rather weird. ip_queue_xmit2 is also the caller of nf_hook_slow (via
ip_queue_xmit) at which time skb->sk must be OK. After nf_hook_slow things
suddenly are wrong.
For the interrested I can send a disassembly listing with matching C lines.
On Tuesday 27 November 2001 07:02, Martin Josefsson wrote:
> On Tue, 27 Nov 2001, Rolf Fokkens wrote:
>
> I've forwarded this report to the place where it should be reported, the
> netfilter-devel@lists.samba.org mailinglist as I havn't seen this report
> there.
Haven't had much response from either list. So I just report this to both.
next prev parent reply other threads:[~2001-11-27 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 11:43 [BUG] vanilla 2.4.15 iptables/REDIRECT kernel oops Rolf Fokkens
2001-11-27 15:02 ` Martin Josefsson
2001-11-28 7:55 ` Rolf Fokkens [this message]
2001-11-28 14:05 ` Stephan von Krawczynski
2001-11-30 10:53 ` [RESOLVED] " Harald Welte
2001-11-30 11:04 ` Rusty Russell
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=01112723555300.01996@home01 \
--to=fokkensr@linux06.vertis.nl \
--cc=gandalf@marcelothewonderpenguin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.samba.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