From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] neighbour: fix nlmsg_pid in notifications Date: Wed, 22 Mar 2017 10:49:11 -0700 (PDT) Message-ID: <20170322.104911.695252715511567175.davem@davemloft.net> References: <1489986088-37528-1-git-send-email-roopa@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, vivek@cumulusnetworks.com To: roopa@cumulusnetworks.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:42156 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935518AbdCVRtN (ORCPT ); Wed, 22 Mar 2017 13:49:13 -0400 In-Reply-To: <1489986088-37528-1-git-send-email-roopa@cumulusnetworks.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Roopa Prabhu Date: Sun, 19 Mar 2017 22:01:28 -0700 > From: Roopa Prabhu > > neigh notifications today carry pid 0 for nlmsg_pid > in all cases. This patch fixes it to carry calling process > pid when available. Applications (eg. quagga) rely on > nlmsg_pid to ignore notifications generated by their own > netlink operations. This patch follows the routing subsystem > which already sets this correctly. > > Reported-by: Vivek Venkatraman > Signed-off-by: Roopa Prabhu Applied, thank you.