From: David Laight <David.Laight@xxxxxxxxxx> Date: Mon, 23 Jan 2017 16:45:39 +0000 > Provided you've got the length of the user's buffer the compat code > ought to be trivial (if tedious). Wireless guys had to deal with a similar problem with nl80211. You don't know who is going to get the message when you build it, because you can't possibly know what applications are listening on the netlink sockets for notifications and even if you did that set changes dynamically and could be different by the time the notification is delivered. The long and short of it is that you must always generate both the native 64-bit as well as the 32-bit compat version of every message, then at delivery time you enqueue the appropriate one to each receiving socket. This is how nl80211 solved the problem, and it's what XFRM should do as well. _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
