On 3/21/18 7:59 AM, Alexander Duyck wrote:
On Tue, Mar 20, 2018 at 10:02 PM, Yonghong Song wrote:
On 3/20/18 4:50 PM, Alexander Duyck wrote:
On Tue, Mar 20, 2018 at 4:21 PM, Yonghong Song wrote:
One of our in-house projects, bpf-based NAT, hits a kernel BUG_ON at
function skb_segment()
On Tue, Mar 20, 2018 at 10:02 PM, Yonghong Song wrote:
>
>
> On 3/20/18 4:50 PM, Alexander Duyck wrote:
>>
>> On Tue, Mar 20, 2018 at 4:21 PM, Yonghong Song wrote:
>>>
>>> One of our in-house projects, bpf-based NAT, hits a kernel BUG_ON at
>>> function skb_segment(), line 3667. The bpf program a
On 3/20/18 4:50 PM, Alexander Duyck wrote:
On Tue, Mar 20, 2018 at 4:21 PM, Yonghong Song wrote:
One of our in-house projects, bpf-based NAT, hits a kernel BUG_ON at
function skb_segment(), line 3667. The bpf program attaches to
clsact ingress, calls bpf_skb_change_proto to change protocol
fr
On Tue, Mar 20, 2018 at 4:21 PM, Yonghong Song wrote:
> One of our in-house projects, bpf-based NAT, hits a kernel BUG_ON at
> function skb_segment(), line 3667. The bpf program attaches to
> clsact ingress, calls bpf_skb_change_proto to change protocol
> from ipv4 to ipv6 or from ipv6 to ipv4, an
