From: Eric Dumazet
Date: Tue, 22 Nov 2016 11:17:30 -0800
> From: Eric Dumazet
>
> Andre Noll reported panics after my recent fix (commit 34fad54c2537
> "net: __skb_flow_dissect() must cap its return value")
>
> After some more headaches, Alexander
From: Eric Dumazet
Date: Tue, 22 Nov 2016 11:17:30 -0800
> From: Eric Dumazet
>
> Andre Noll reported panics after my recent fix (commit 34fad54c2537
> "net: __skb_flow_dissect() must cap its return value")
>
> After some more headaches, Alexander root caused the problem to
>
On Tue, Nov 22, 11:17, Eric Dumazet wrote
> -late_initcall_sync(init_default_flow_dissectors);
> +core_initcall(init_default_flow_dissectors);
Indeed, that fixed it. Feel free to add
Tested-by: Andre Noll
Thanks a lot
Andre
--
Max Planck Institute for Developmental
On Tue, Nov 22, 11:17, Eric Dumazet wrote
> -late_initcall_sync(init_default_flow_dissectors);
> +core_initcall(init_default_flow_dissectors);
Indeed, that fixed it. Feel free to add
Tested-by: Andre Noll
Thanks a lot
Andre
--
Max Planck Institute for Developmental Biology
Spemannstraße 35,
From: Eric Dumazet
Andre Noll reported panics after my recent fix (commit 34fad54c2537
"net: __skb_flow_dissect() must cap its return value")
After some more headaches, Alexander root caused the problem to
init_default_flow_dissectors() being called too late, in case
a
From: Eric Dumazet
Andre Noll reported panics after my recent fix (commit 34fad54c2537
"net: __skb_flow_dissect() must cap its return value")
After some more headaches, Alexander root caused the problem to
init_default_flow_dissectors() being called too late, in case
a network driver like IGB
6 matches
Mail list logo