From: Florian Westphal <[EMAIL PROTECTED]>
Date: Sat, 23 Jun 2007 20:25:46 +0200
> From: Florian Westphal <[EMAIL PROTECTED]>
>
> The tipc netlink config handler uses the nlmsg_pid from the
> request header as destination for its reply. If the application
> initialized nlmsg_pid to 0, the reply i
From: Florian Westphal <[EMAIL PROTECTED]>
Date: Sat, 23 Jun 2007 20:25:46 +0200
> From: Florian Westphal <[EMAIL PROTECTED]>
>
> The tipc netlink config handler uses the nlmsg_pid from the
> request header as destination for its reply. If the application
> initialized nlmsg_pid to 0, the reply i
From: Florian Westphal <[EMAIL PROTECTED]>
The tipc netlink config handler uses the nlmsg_pid from the
request header as destination for its reply. If the application
initialized nlmsg_pid to 0, the reply is looped back to the kernel,
causing hangup. Fix: use nlmsg_pid of the skb that triggered th