On Mon, Sep 8, 2014 at 8:53 PM, Joe Stringer wrote:
> Was there a particular tool or config flag that you used to detect this
> error / generate this output?
>
I compile kernel with debugging options. CONFIG_PROVE_LOCKING detects
most of deadlocks in kernel, you do not need any other tool.
> On 8
Was there a particular tool or config flag that you used to detect this
error / generate this output?
On 8 September 2014 14:01, Pravin B Shelar wrote:
> packet execute is setting egress_tun_info in skb->cb, rather
> than packet->cb. skb is netlink msg skb. This causes corruption
> in netlink sk
On Sun, Sep 7, 2014 at 11:26 PM, Joe Stringer wrote:
>
>
> On 8 September 2014 14:01, Pravin B Shelar wrote:
>>
>> packet execute is setting egress_tun_info in skb->cb, rather
>> than packet->cb. skb is netlink msg skb. This causes corruption
>> in netlink skb state stored in skb->cb (NETLINK_CB)
On 8 September 2014 14:01, Pravin B Shelar wrote:
> packet execute is setting egress_tun_info in skb->cb, rather
> than packet->cb. skb is netlink msg skb. This causes corruption
> in netlink skb state stored in skb->cb (NETLINK_CB) which
> results in following deadlock in netlink code.
>
> =
packet execute is setting egress_tun_info in skb->cb, rather
than packet->cb. skb is netlink msg skb. This causes corruption
in netlink skb state stored in skb->cb (NETLINK_CB) which
results in following deadlock in netlink code.
=
[ INFO: possible recur
