[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170322.104911.695252715511567175.davem@davemloft.net>
Date: Wed, 22 Mar 2017 10:49:11 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: roopa@...ulusnetworks.com
Cc: netdev@...r.kernel.org, vivek@...ulusnetworks.com
Subject: Re: [PATCH net-next] neighbour: fix nlmsg_pid in notifications
From: Roopa Prabhu <roopa@...ulusnetworks.com>
Date: Sun, 19 Mar 2017 22:01:28 -0700
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> 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 <vivek@...ulusnetworks.com>
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
Applied, thank you.
Powered by blists - more mailing lists