[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ee9e514-9008-6b30-9665-38607169146d@gmail.com>
Date: Tue, 26 May 2020 18:31:14 -0600
From: David Ahern <dsahern@...il.com>
To: Saeed Mahameed <saeedm@...lanox.com>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"brouer@...hat.com" <brouer@...hat.com>
Subject: Re: bpf-next/net-next: panic using bpf_xdp_adjust_head
On 5/26/20 3:23 PM, Saeed Mahameed wrote:
> Anyway I can't figure out the reason for this without extra digging
> since in mlx5 we do xdp_set_data_meta_invalid(); before passing the xdp
> buff to the bpf program, so it is not clear why would you hit the
> memove in bpf_xdp_adjust_head().
I commented out the metalen check in bpf_xdp_adjust_head to move on.
There are number of changes in the mlx5 driver related to xdp_buff setup
and running the programs, so it is the likely candidate. Let me know if
you have something to test.
Thanks
Powered by blists - more mailing lists