lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAAA5faGnoYRZvYFrAyC=qZjXBVYDSH2tBxeNzZjtZu8F+yxJSQ@mail.gmail.com>
Date:   Mon, 21 Jan 2019 13:18:44 -0800
From:   Reinoud Koornstra <reinoudkoornstra@...il.com>
To:     netdev@...r.kernel.org
Subject: netlink_unicast usage

Dear Everyone,

Forgive me for abusing this list, but I'm not sure where else to
direct my mail to for this question.
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ