search for: skb_release_data

...+0x10/0x20 ? default_idle+0x1e/0xd0 ? arch_cpu_idle+0xf/0x20 ? default_idle_call+0x2c/0x40 ? cpu_startup_entry+0x1ac/0x240 ? rest_init+0x77/0x80 ? start_kernel+0x4a7/0x4b4 ? set_init_arg+0x55/0x55 ? x86_64_start_reservations+0x24/0x26 ? xen_start_kernel+0x555/0x561 RIP skb_release_data+0x73/0xf0 Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: disabled (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. If anyone has had a similar backtrace or knows of a potential fix please respond. This server has ECC and there were no ECC or other errors in...

...0xf0 Apr 02 14:23:03 helium kernel: warn_slowpath_null+0x1d/0x20 Apr 02 14:23:03 helium kernel: nft_meta_get_eval+0x40e/0x450 [nft_meta] Apr 02 14:23:03 helium kernel: nft_do_chain+0x102/0x4e0 [nf_tables] Apr 02 14:23:03 helium kernel: ? skb_free_head+0x21/0x30 Apr 02 14:23:03 helium kernel: ? skb_release_data+0x101/0x110 Apr 02 14:23:03 helium kernel: ? kfree_skbmem+0x59/0x60 Apr 02 14:23:03 helium kernel: ? __kfree_skb+0x1a/0x20 Apr 02 14:23:03 helium kernel: ? tcp_rcv_established+0x27b/0x6f0 Apr 02 14:23:03 helium kernel: ? sk_filter_trim_cap+0xb7/0x260 Apr 02 14:23:03 helium kernel: ? nft_do_cha...

...0018>] [<c0165e69>] [<c01614c3>] [<c01e93d3>] [<c0164375>] [<c01641e0>] [<c0105726>] [<c0164200>] Code: 8b 41 18 a9 00 40 00 00 75 14 ff 49 14 0f 94 c0 84 c0 74 0a >>EIP; c012e2d2 <__free_pages+2/30> <===== Trace; c01d865e <skb_release_data+3e/70> Trace; c01d869b <kfree_skbmem+b/70> Trace; c01d8809 <__kfree_skb+109/110> Trace; c020723c <arp_rcv+44c/460> Trace; c011ee90 <update_process_times+20/b0> Trace; c01dc7da <net_rx_action+12a/210> Trace; c010831a <handle_IRQ_event+3a/70> Trace; c011bca3 &lt...

...task ffffffff806de360) Stack: 000000000000000b ffff8800ce587b00 ffffc20000003c80 ffffffff804a57b6 ffff8800ce587b00 ffffffff8074b760 ffffc20000003ca0 ffffffff804a5e18 0000000000000000 ffff8800ce587b00 ffffc20000003cc0 ffffffff804a5636 Call Trace: <IRQ> <0> [<ffffffff804a57b6>] skb_release_data+0x9b/0xac [<ffffffff804a5e18>] skb_release_all+0x19/0x1e [<ffffffff804a5636>] __kfree_skb+0x11/0x78 [<ffffffff804a56c5>] kfree_skb+0x28/0x2a [<ffffffff804abc91>] netif_receive_skb+0x2c6/0x2eb [<ffffffff804ac067>] napi_gro_receive+0x26/0x3a [<ffffffffa000c1ab&g...

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

...ck.c:53 print_address_description+0x73/0x250 mm/kasan/report.c:252 kasan_report_double_free+0x55/0x80 mm/kasan/report.c:333 kasan_slab_free+0xa3/0xc0 mm/kasan/kasan.c:514 __cache_free mm/slab.c:3488 [inline] kfree+0xca/0x250 mm/slab.c:3803 skb_free_head+0x74/0xb0 net/core/skbuff.c:550 skb_release_data+0x58c/0x790 net/core/skbuff.c:570 skb_release_all+0x4a/0x60 net/core/skbuff.c:627 __kfree_skb net/core/skbuff.c:641 [inline] consume_skb+0x153/0x490 net/core/skbuff.c:701 __dev_kfree_skb_any+0x85/0xa0 net/core/dev.c:2515 dev_consume_skb_any include/linux/netdevice.h:3276 [inline] free_o...