[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAAA5faG9TBrz6armsToGn=hTbqAZrhTjYeYUzvMLgDuo-rjDZw@mail.gmail.com>
Date: Mon, 21 Jan 2019 13:05:26 -0800
From: Reinoud Koornstra <reinoudkoornstra@...il.com>
To: netdev@...r.kernel.org
Subject: netlink_unicast fail
Dear Everyone,
In a kernel loadable module, I'm using netlink_unicast to send
messages back to userland.
In most cases we assume this passes, but the function is written as an
int and can fail.
In that case there's no way to notify userland that a message isn't
coming back and depending on the api used in userland we're waiting
forever for an answer.
In case netlink_unicast fails, the skb is freed, but when it passes it isn't?
I'm wondering how to treat the case where it fails, or should I use
another api to send messages back to userspace all together?
Thanks,
Reinoud.
Powered by blists - more mailing lists