All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOVACS Krisztian <hidden@sch.bme.hu>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: kaber@trash.net, hidden@sch.bme.hu, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] TPROXY cleanups
Date: Mon, 6 Oct 2008 16:15:59 +0200	[thread overview]
Message-ID: <20081006141559.GC18559@sch.bme.hu> (raw)
In-Reply-To: <20081006123921.GA23796@x200.localdomain>

Hi,

On h, okt 06, 2008 at 04:39:21 +0400, Alexey Dobriyan wrote:
> On Mon, Oct 06, 2008 at 02:26:03PM +0200, KOVACS Krisztian wrote:
> > On h, okt 06, 2008 at 04:19:44 +0400, Alexey Dobriyan wrote:
> > > * drop version.h -- unneeded and file will be needlessly rebuilt.
> > > * make tproxy_core unloadable
> > > * use "in" device outright, -- target and match are only in PRE_ROUTING,
> > >   so should avoid dereference.
> 
> > > @@ -89,7 +88,11 @@ static int __init nf_tproxy_init(void)
> > >  	return 0;
> > >  }
> > >  
> > > +static void __exit nf_tproxy_exit(void)
> > > +{
> > > +}
> > >  module_init(nf_tproxy_init);
> > > +module_exit(nf_tproxy_exit);
> > 
> > Please don't do this. The module was made unloadable because it attaches a
> > function pointer to skb's and removing the module while there's an skb in
> > flight would cause a kernel crash.
> 
> Have you actually seen it?

No.

> xt_TPROXY will pin it because it uses a symbol from it, so it won't
> dissapear.

Yeah, that's true, and I think that it's impossible to remove the rule
attaching the socket references while the skb's in flight. Ok, so let's
add module_exit() then.

-- 
KOVACS Krisztian

  reply	other threads:[~2008-10-06 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 12:19 [PATCH] TPROXY cleanups Alexey Dobriyan
2008-10-06 12:26 ` KOVACS Krisztian
2008-10-06 12:39   ` Alexey Dobriyan
2008-10-06 14:15     ` KOVACS Krisztian [this message]
2008-10-06 15:41       ` Patrick McHardy
2008-10-07  6:32         ` KOVACS Krisztian

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=20081006141559.GC18559@sch.bme.hu \
    --to=hidden@sch.bme.hu \
    --cc=adobriyan@gmail.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.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.