[linux-dvb] Re: OOPS with budget card + cam (in dvb_ca_en50221_io_write)

[Andrew de Quincey <adq_dvb@lidskialf.net>]

>  [<c03ccccb>] ip_nat_fn+0x8b/0x210
>  [<c03922f0>] ip_local_deliver_finish+0x0/0x1b0
>  [<c03923ac>] ip_local_deliver_finish+0xbc/0x1b0
>  [<c03922f0>] ip_local_deliver_finish+0x0/0x1b0
>  [<c0389f09>] nf_hook_slow+0xc9/0x100
>  [<c03922f0>] ip_local_deliver_finish+0x0/0x1b0
>  [<c03924a0>] ip_rcv_finish+0x0/0x220
>  [<c0114023>] scheduler_tick+0x163/0x3f0
>  [<c011de86>] update_process_times+0x46/0x60
>  [<c011dceb>] update_wall_time+0xb/0x40
>  [<c011e11f>] do_timer+0xdf/0xf0
>  [<c011a4bd>] __do_softirq+0x7d/0x80
>  [<c0114023>] scheduler_tick+0x163/0x3f0
>  [<c012cf63>] wake_up_page+0x13/0x40
>  [<c012d08f>] unlock_page+0x1f/0x30
>  [<c013a3b1>] do_wp_page+0x1d1/0x230
>  [<c011de86>] update_process_times+0x46/0x60
>  [<c013aed9>] handle_mm_fault+0x159/0x170
>  [<c011388f>] recalc_task_prio+0x8f/0x190
>  [<c03efa72>] schedule+0x272/0x430
>  [<c03effad>] schedule_timeout+0x6d/0xc0
>  [<e1a5a380>] dvb_ca_en50221_io_write+0x0/0x1e0 [dvb_core]
>  [<c0147a7c>] vfs_write+0xdc/0x140
>  [<c011e30e>] sys_nanosleep+0xde/0x170
>  [<c0147b92>] sys_write+0x42/0x70
>  [<c0103efb>] syscall_call+0x7/0xb

This stack trace is weird! Why is it listing the kernel ip stack's NAT code in 
it?