From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 3/8] [PATCH] Helper modules load-on-demand support for ctnetlink
Date: Thu, 09 Oct 2008 18:11:37 +0200 [thread overview]
Message-ID: <48EE2D39.8090401@trash.net> (raw)
In-Reply-To: <48EE1A33.4010603@netfilter.org>
Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>> Patrick McHardy wrote:
>>> This one doesn't apply:
>>>
>>> patching file include/net/netfilter/nf_conntrack_helper.h
>>> patching file net/netfilter/nf_conntrack_core.c
>>> Hunk #1 FAILED at 581.
>>> Hunk #2 succeeded at 753 (offset -5 lines).
>>> Hunk #3 succeeded at 764 (offset -5 lines).
>>> 1 out of 3 hunks FAILED -- saving rejects to file
>>> net/netfilter/nf_conntrack_core.c.rej
>>> patching file net/netfilter/nf_conntrack_helper.c
>>> patching file net/netfilter/nf_conntrack_netlink.c
>>> Hunk #2 succeeded at 1131 with fuzz 1.
>>> patching file net/netfilter/nfnetlink.c
>> Oops, I think I didn't refresh my tree, so it didn't include any
>> of the netfilter patches I sent to Dave :)
>
> So, what do I have to do now? I'm cloning Dave's tree now to put the
> patches on top on it. Fine with it?
I think it was my mistake, let me try again ... yes, it applies
cleanly. Both Dave's tree or my tree should work, but use Dave's
if you want to be safe since I haven't updated mine yet.
>> The remaining issues, especially the nfnl_lock think, should be
>> fixed though.
>
> OK. BTW, returning EOPNOTSUPP looks better to me. ENOENT is misleading
> since the user won't be able to differenciate between "I don't know
> anything about that helper" and "this conntrack entry does not exist".
> So, I prefer using EOPNOTSUPP.
Makes sense.
next prev parent reply other threads:[~2008-10-09 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 8:33 [PATCH 1/8] [PATCH] get rid of module refcounting in ctnetlink Pablo Neira Ayuso
2008-10-09 8:34 ` [PATCH 2/8] [PATCH] connection tracking helper name persistent aliases Pablo Neira Ayuso
2008-10-09 13:27 ` Patrick McHardy
2008-10-09 8:34 ` [PATCH 3/8] [PATCH] Helper modules load-on-demand support for ctnetlink Pablo Neira Ayuso
2008-10-09 13:34 ` Patrick McHardy
2008-10-09 13:43 ` Patrick McHardy
2008-10-09 14:50 ` Pablo Neira Ayuso
2008-10-09 16:11 ` Patrick McHardy [this message]
2008-10-09 16:43 ` Pablo Neira Ayuso
2008-10-09 8:34 ` [PATCH 4/8] [PATCH] use EOPNOTSUPP instead of EINVAL if the conntrack has no helper Pablo Neira Ayuso
2008-10-10 13:03 ` Patrick McHardy
2008-10-09 8:35 ` [PATCH 5/8] [PATCH] deliver events for conntracks created via ctnetlink Pablo Neira Ayuso
2008-10-10 13:31 ` Patrick McHardy
2008-10-11 12:05 ` Pablo Neira Ayuso
2008-10-11 14:53 ` Patrick McHardy
2008-10-09 8:35 ` [PATCH 6/8] [PATCH] bump the expectation helper name Pablo Neira Ayuso
2008-10-09 8:35 ` [PATCH 7/8] [PATCH] dynamic calculation of event message size for ctnetlink Pablo Neira Ayuso
2008-10-09 16:45 ` Pablo Neira Ayuso
2008-10-09 8:36 ` [PATCH 8/8] [PATCH] remove module dependency between ctnetlink and nf_nat Pablo Neira Ayuso
2008-10-09 13:26 ` [PATCH 1/8] [PATCH] get rid of module refcounting in ctnetlink Patrick McHardy
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=48EE2D39.8090401@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;
as well as URLs for NNTP newsgroup(s).