Re: My first target module is a fiasco.

[KOVACS Krisztian <hidden@balabit.hu>]

   Hi,

Emmanuel Guiton wrote:
> After having written a first version of a new target module, I tried to 
> test it. Well... I does not look promising: segmentation fault, the 
> detail follows. However, what disturbs me is that I commented out 
> totally my module, leaving only some printk to have some feedback and 
> the backbone of the module: register, unregister, the static struct 
> ipt_target, and the - empty - functions that go along with it.
> To summarize: empty module; segmentation fault.

   Could you show us the code of the init function, and the static 
structure it registers? However, it looks like the kernel thinks your 
module failed to load (its __init function did not return 0), however, it 
has successfully registered its target... This is bad, since the memory 
allocated for your module is freed when your __init function returns any 
value other than zero.

> Dec 15 16:53:34 pc104 insmod: 
> /lib/modules/2.4.23/kernel/net/ipv4/netfilter/ipt_SYNDIS.o: init_module: 
> Device or resource busy
> Dec 15 16:53:34 pc104 insmod: Hint: insmod errors can be caused by 
> incorrect module parameters, including invalid IO or IRQ 
> parameters.       You may find more information in syslog or the output 
> from dmesg
> Dec 15 16:53:34 pc104 insmod: 
> /lib/modules/2.4.23/kernel/net/ipv4/netfilter/ipt_SYNDIS.o: insmod 
> ipt_SYNDIS failed
> Dec 15 16:53:34 pc104 kernel: SYNDIS: target registered.<1>Unable to 
> handle kernel paging request at virtual address c884c348

-- 
   Regards,
     Krisztian KOVACS