On Wed, 2016-10-26 at 18:53 +0200, Abdelrhman Ahmed wrote:
> I think it's at the right place as the current one is a little different from
> the
> commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
>
> In the next lines, skb_push is called after copying the hardware header and
> there
> is no chan
I think it's at the right place as the current one is a little different from
the
commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c.
In the next lines, skb_push is called after copying the hardware header and
there
is no change to the data pointer inside the retry loop. We only need to reset
befor
On Wed, 2016-10-26 at 01:57 +0200, Abdelrhman Ahmed wrote:
> > What is the issue you want to fix exactly ?
> > Please describe the use case.
>
> When netfilter hook uses skb_push to add a specific header between network
> header and hardware header.
> For the first time(s) before caching hardw
> What is the issue you want to fix exactly ?
> Please describe the use case.
When netfilter hook uses skb_push to add a specific header between network
header and hardware header.
For the first time(s) before caching hardware header, this header will be
removed / overwritten by hardware heade
On Fri, 2016-10-07 at 16:14 +0200, Abdelrhman Ahmed wrote:
> When hardware header is added without using cached one, neigh_resolve_output
> and neigh_connected_output reset skb to network header before adding it.
> When cached one is used, neigh_hh_output does not reset the skb to network
> header.
On 10/07/2016 07:27 PM, Sergei Shtylyov wrote:
When hardware header is added without using cached one, neigh_resolve_output
and neigh_connected_output reset skb to network header before adding it.
When cached one is used, neigh_hh_output does not reset the skb to network
header.
The fix is to r
Hello.
On 10/07/2016 05:14 PM, Abdelrhman Ahmed wrote:
When hardware header is added without using cached one, neigh_resolve_output
and neigh_connected_output reset skb to network header before adding it.
When cached one is used, neigh_hh_output does not reset the skb to network
header.
The fi
When hardware header is added without using cached one, neigh_resolve_output
and neigh_connected_output reset skb to network header before adding it.
When cached one is used, neigh_hh_output does not reset the skb to network
header.
The fix is to reset skb to network header before adding cached ha
