From: Martin Clausen <martin@ostenfeld.dk>
To: James Morris <jmorris@intercode.com.au>
Cc: netfilter-devel@lists.samba.org, linux-kernel@vger.kernel.org,
Paul Rusty Russell <Paul.Russell@rustcorp.com.au>
Subject: Re: Kernel Oops when using the Netfilter QUEUE target
Date: Fri, 27 Apr 2001 00:48:01 +0200 [thread overview]
Message-ID: <20010427004801.A3464@ostenfeld.dk> (raw)
In-Reply-To: <20010425004937.A3904@ostenfeld.dk> <Pine.LNX.4.31.0104251621260.329-100000@blackbird.intercode.com.au>
In-Reply-To: <Pine.LNX.4.31.0104251621260.329-100000@blackbird.intercode.com.au>; from jmorris@intercode.com.au on Wed, Apr 25, 2001 at 04:24:46PM +1000
On Wed, Apr 25, 2001 at 04:24:46PM +1000, James Morris wrote:
> > I have encountered a problem (perhaps a bug)! The attached code makes my kernel oops
> > in some cases when injecting new packets through Netfilter's QUEUE target. The problem
> > only appears when the original packet is a TCP packet; i have tried with ICMP and UDP packets
> > also but this does not trigger any oops. I have tried to code on several computers and they
> > all oops. The following description regards the case when submitting new packets instead
> > of TCP packets.
>
> Please try the patch below.
So i did and it seems to work just fine (= no more oops') under 2.4.3/2.4.2-ac21! The packets
being sent also seems to be correct; James you're the man :-)
BTW could you describe the problem? And why it caused an oops?
Best regards,
Martin
--
There's no place like ~
next prev parent reply other threads:[~2001-04-26 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010425004937.A3904@ostenfeld.dk>
2001-04-25 6:24 ` Kernel Oops when using the Netfilter QUEUE target James Morris
2001-04-26 22:48 ` Martin Clausen [this message]
2001-04-27 13:42 ` Rusty Russell
2001-04-24 17:25 Martin Clausen
2001-04-26 3:13 ` Keith Owens
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=20010427004801.A3464@ostenfeld.dk \
--to=martin@ostenfeld.dk \
--cc=Paul.Russell@rustcorp.com.au \
--cc=jmorris@intercode.com.au \
--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