search for: dst_output

...fe/0x1460 [xfs] Aug 27 19:27:38 sauron kernel: [<c023af60>] ip_finish_output2+0x0/0x1b0 Aug 27 19:27:38 sauron kernel: [<c022d701>] nf_hook_slow+0xf1/0x120 Aug 27 19:27:39 sauron kernel: [<c023af60>] ip_finish_output2+0x0/0x1b0 Aug 27 19:27:39 sauron kernel: [<c023af30>] dst_output+0x0/0x30 Aug 27 19:27:39 sauron kernel: [<c023af44>] dst_output+0x14/0x30 Aug 27 19:27:39 sauron kernel: [<c0223949>] dev_queue_xmit+0x249/0x300 Aug 27 19:27:39 sauron kernel: [<c023b004>] ip_finish_output2+0xa4/0x1b0 Aug 27 19:27:39 sauron kernel: [<c023af60>] ip_finish...

...t;] dev_hard_start_xmit+0x198/0x1ee [<c05bcaf6>] __qdisc_run+0xe4/0x19a [<c05b0544>] dev_queue_xmit+0x1e0/0x2e8 [<c05b4b24>] neigh_resolve_output+0x1b2/0x1dc [<d136eb2e>] ip6_output2+0x256/0x2a7 [ipv6] [<d136f656>] ip6_output+0x9c7/0x9f3 [ipv6] [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<c05c3d12>] nf_hook_slow+0x3a/0x90 [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<d137e4d6>] ndisc_send_ns+0x3a8/0x47a [ipv6] [<c06090d8>] _spin_lock_irqsave+0x8/0x28 [<c042914a>] lock_timer_base+0x15/0x2f [<d1375ddb>] addrconf_dad_timer+0xc3/0xdf...

...we create little descriptors of the form: > > struct nf_hook_desc { > int (*okfn)(struct sk_buff *); > int pf; > int hook; > }; > > Then NF_HOOK*() callsites do something like this: > > static const struct nf_hook_desc nf_ip_local_out = { > .okfn = dst_output, > .pf = PF_INET, > .hook = NF_IP_LOCAL_OUT, > }; > > ... > > /* Send it out. */ > return NF_HOOK(&nf_ip_local_out, skb, NULL, rt->u.dst.dev); > > This gets us down to 4 arguments from 6. I think we can kill > one more. > > It is n...

https://bugzilla.netfilter.org/show_bug.cgi?id=852 Summary: IPv6 TEE target sends packets to original IP address on wrong network device Product: netfilter/iptables Version: unspecified Platform: x86_64 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: unknown

On Fri, 07 Jan 2005 17:05:59 +0000 David Woodhouse <dwmw2@infradead.org> wrote: > On Sat, 2004-12-18 at 08:50 +0100, Andi Kleen wrote: > > It's not really an oops, just a warning that stack space got quiet > > tight. > > > > The problem seems to be that the br netfilter code is nesting far too > > deeply and recursing several times. Looks like a design

Hi, I try to build experimental networks with Xen and stumbled over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been

Hi, I try to build experimental networks with Xen and stumbled over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been

...net/neighbour.h:472 [inline] neigh_output include/net/neighbour.h:480 [inline] ip_finish_output2+0xece/0x1460 net/ipv4/ip_output.c:229 ip_finish_output+0x85e/0xd10 net/ipv4/ip_output.c:317 NF_HOOK_COND include/linux/netfilter.h:239 [inline] ip_output+0x1cc/0x860 net/ipv4/ip_output.c:405 dst_output include/net/dst.h:460 [inline] ip_local_out+0x95/0x160 net/ipv4/ip_output.c:124 ip_queue_xmit+0x8c6/0x18e0 net/ipv4/ip_output.c:504 tcp_transmit_skb+0x1b12/0x38b0 net/ipv4/tcp_output.c:1176 tcp_write_xmit+0x680/0x5190 net/ipv4/tcp_output.c:2367 __tcp_push_pending_frames+0xa0/0x250 net/ipv...

Looks like the GSO is involved? I got this while running Dom0 only (no guests), with a BOINC/Rosetta@home application running on all 4 cores. changeset: 10649:8e55c5c11475 Build: x86_32p (pae). ------------[ cut here ]------------ kernel BUG at net/core/dev.c:1133! invalid opcode: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c04dceb0>] Not tainted VLI EFLAGS: 00210297 (2.6.16.13-xen