From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] Check returnvalue of nfct_nat()
Date: Mon, 27 Nov 2006 17:51:49 +0100 [thread overview]
Message-ID: <1164646309.30244.30.camel@localhost.localdomain> (raw)
In-Reply-To: <456B114C.5000204@trash.net>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Mon, 2006-11-27 at 17:24 +0100, Patrick McHardy wrote:
> Thanks, I just noticed the same crash when loading iptable_nat over
> ssh (it works fine with the additional checks now).
:)
I seem to always find new bugs when porting my patches to a newer
kernels :)
This time it was this bug and a strange locking bug in what appears to
be socket locking, Peter Zijlstra just mailed me a possible fix for
that.
> > Some of the checks in the patch might not be strictly neccessary, I havn't
> > audited the calls, it was 4 AM :) The check added in nf_nat_fn() should take
> > care of things for us...
>
> The nfct_help part is a bit more trickier since not only can
> nfct_help return NULL, but nfct_help(ct)->help can become NULL
> as well when the helper is unloaded even while it is still
> executing. I want to think about this some more, but I went
> over the nfct_nat part and added the ones that look necessary,
> it came down to only two :)
:) My brain was shutting down and the NAT core is still a lot of voodoo
for me :) I just added checks everywhere so I could continue to test my
patches, great that you reviewed it and sorted out which ones are really
neccessary.
I'll give your revised patch a go and see if it survives my tests.
Thanks.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-11-27 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 10:13 [PATCH] Check returnvalue of nfct_nat() Martin Josefsson
2006-11-27 16:24 ` Patrick McHardy
2006-11-27 16:51 ` Martin Josefsson [this message]
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=1164646309.30244.30.camel@localhost.localdomain \
--to=gandalf@wlug.westbo.se \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.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 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.