l2tp: Fix error creating L2TP tunnels
authorMark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
Mon, 15 Feb 2016 03:24:44 +0000 (16:24 +1300)
committerDavid S. Miller <davem@davemloft.net>
Wed, 17 Feb 2016 20:34:47 +0000 (15:34 -0500)
commit853effc55b0f975abd6d318cca486a9c1b67e10f
treee3f62f0dcd843661a7191f6a9e5e3d8421f63546
parentd148bbd37a52b030b131ac5408c0f8293325ca0b
l2tp: Fix error creating L2TP tunnels

A previous commit (33f72e6) added notification via netlink for tunnels
when created/modified/deleted. If the notification returned an error,
this error was returned from the tunnel function. If there were no
listeners, the error code ESRCH was returned, even though having no
listeners is not an error. Other calls to this and other similar
notification functions either ignore the error code, or filter ESRCH.
This patch checks for ESRCH and does not flag this as an error.

Reviewed-by: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
Signed-off-by: Mark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/l2tp/l2tp_netlink.c