[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161114031130.yjb4anou24ede4ue@wfg-t540p.sh.intel.com>
Date: Mon, 14 Nov 2016 11:11:30 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Ye Xiaolong <xiaolong.ye@...el.com>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
Alexander Duyck <alexander.h.duyck@...el.com>,
Willem de Bruijn <willemb@...gle.com>,
netdev <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Jojy Varghese <jojvargh@...co.com>,
Tom Herbert <tom@...bertland.com>,
Yibin Yang <yibyang@...co.com>, lkp@...org,
David Miller <davem@...emloft.net>
Subject: Re: [LKP] [net] 2ab9fb18c4: kernel BUG at
include/linux/skbuff.h:1935!
>>Hi guys.
>>
>>I took a look at the commit again and I do not see how this can happen.
>>
>>Are you sure patch was properly applied ?
>>
>>In particular, the following extract is obscure for me :
>>
>>
>>> https://github.com/0day-ci/linux Eric-Dumazet/net-__skb_flow_dissect-must-cap-its-return-value/20161110-080839
>>> commit 2ab9fb18c46b91b16a0f0f329336d3be9fc32deb ("net: __skb_flow_dissect() must cap its return value")
>>>
>
>Hi,
>
>The above two lines means 0day repo setup a new branch
>"Eric-Dumazet/net-__skb_flow_dissect-must-cap-its-return-value/20161110-080839"
>which is based on net/master, then applied you patch on top of it,
>commit id is 2ab9fb18c46b91b16a0f0f329336d3be9fc32deb.
Xiaolong, it may be more helpful to show the base tree where we apply
the patch to. And the final url:
https://github.com/0day-ci/linux/tree/Eric-Dumazet/net-__skb_flow_dissect-must-cap-its-return-value/20161110-080839
Thanks,
Fengguang
Powered by blists - more mailing lists