From: Pierre Rondou <prondou@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netfilter-devel@vger.kernel.org, evyncke@cisco.com,
guy.leduc@ulg.ac.be, Cyril Soldani <cyril.soldani@ulg.ac.be>
Subject: Re: EXPORT_SYMBOL missing in the kernel?
Date: Tue, 24 May 2011 17:42:53 +0200 [thread overview]
Message-ID: <4DDBD1FD.1070203@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1105241639150.32028@frira.zrqbmnf.qr>
Hello Jan,
I appreciate your help !
This problem is not related with the problem I had at this moment.
The "old" problem was about an output problem with ip6_local_out. I was
at this time on an old debian testing (between lenny and squeeze) and
the update to "complete" squeeze solved the problem, so I thought that
it was a problem related to my OS situation.
Now that you say that, I have realized that ip6_local_out (which I don't
use anymore, I use ip6_output) was creating kernel panic when asked to
send an IPv6 packet with a size higher than the link mtu, should have
talked about it earlier though.
The little complain about NATIVI
(http://www.spinics.net/lists/netfilter-devel/msg18248.html) was that no
kernel / Xtables developers told me they wanted the module inside the
kernel/Xtables or even sent me a remark about it and therefore could
take care about the missing "EXPORT_SYMBOL".
This module is developed inside Xtables and therefore doesn't need to
recompile a kernel.
While I'm sending you an e-mail, I may contribute to your very
interesting "Writing Netfilter modules" ebook.
I had to deal with checksums changes/update in both IPv4 and IPv6 and
may contribute to this section (5.7) if you still need someone to :-).
Regards,
Pierre
Le 24/05/11 16:41, Jan Engelhardt a écrit :
>
> On Tuesday 2011-05-24 15:48, Pierre Rondou wrote:
>
>> Of course, the best way would be to patch the currently dev kernel (2.6.39 if I
>> take your word from previous mail) to use my module.
>> But I'm not a kernel developper and my previously proposed module (NATIVI,
>> which had the same problem) didn't seem to get interest from kernel or Xtables
>> developers :(
>>
> On the contrary. If there was no interest, I would not have written a
> reply. But you seem to have chosen to ignore that and went away with "it
> fixed itself".
>
> http://www.spinics.net/lists/netfilter-devel/msg18073.html
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-24 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 13:03 EXPORT_SYMBOL missing in the kernel? Pierre Rondou
2011-05-24 13:40 ` Eric Dumazet
2011-05-24 13:48 ` Pierre Rondou
2011-05-24 14:41 ` Jan Engelhardt
2011-05-24 15:42 ` Pierre Rondou [this message]
2011-05-24 21:32 ` Jan Engelhardt
2011-05-25 13:05 ` Pierre Rondou
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=4DDBD1FD.1070203@gmail.com \
--to=prondou@gmail.com \
--cc=cyril.soldani@ulg.ac.be \
--cc=eric.dumazet@gmail.com \
--cc=evyncke@cisco.com \
--cc=guy.leduc@ulg.ac.be \
--cc=jengelh@medozas.de \
--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 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).