Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH 4/7] Helper modules load on-demand support for ctnetlink
Date: Wed, 30 Jul 2008 15:35:12 +0200	[thread overview]
Message-ID: <48906E10.9020902@trash.net> (raw)
In-Reply-To: <4890519C.80407@netfilter.org>

Pablo Neira Ayuso wrote:
> Sorry, it's wrong. Please, take this.

> @@ -1672,9 +1660,24 @@ ctnetlink_create_expect(struct nlattr *c
>  	help = nfct_help(ct);
>  
>  	if (!help || !help->helper) {
> -		/* such conntrack hasn't got any helper, abort */
> +#ifdef CONFIG_KMOD
> +		char *name;
> +
>  		err = -EINVAL;
> +		if (!cda[CTA_EXPECT_HELP_NAME])
> +			goto out;
> +
> +		err = -ENOTSUPP;
> +		name = nla_data(cda[CTA_EXPECT_HELP_NAME]);
> +		if (request_module("nfct-helper-%s", name) < 0)
> +			goto out;
> +
> +		if (nf_ct_set_helper(ct, GFP_KERNEL) < 0)
> +			goto out;

This strikes me as quite inconsistent. First, we only perform
autoloading for expectation creation, but not for conntracks.
Second, this implicit helper assignment is also a bit unusual,
why don't we simply insist that the conntrack has a helper
assigned through the ctnetlink conntrack interface?

  reply	other threads:[~2008-07-30 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 11:03 [PATCH 4/7] Helper modules load on-demand support for ctnetlink Pablo Neira Ayuso
2008-07-30 11:10 ` Patrick McHardy
2008-07-30 11:29   ` Pablo Neira Ayuso
2008-07-30 11:33     ` Pablo Neira Ayuso
2008-07-30 13:35       ` Patrick McHardy [this message]
2008-07-31  8:36         ` Pablo Neira Ayuso
2008-07-31  8:46           ` Patrick McHardy
2008-07-31  9:44             ` Pablo Neira Ayuso
2008-07-31 17:51               ` Pablo Neira Ayuso
2008-07-31 21:27                 ` Pablo Neira Ayuso

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=48906E10.9020902@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox