-
Welcome
-
Subscribe to
Netlink engine issues, and ways to fix those
Session information has not yet been published for this event.
One Line Summary
An attempt to resolve Netlink issues to use it outside of the network subsystem
Abstract
Currently netlink is widely used in the network subsystem, but there are also a few users outside of networking, such as audit and taskstats. Developers who used netlink for anything except the networking know there are some issues. For example, taskstats code has broken user and pid namespace support. Another big problem is credentials. Netlink sockets checks credentials from the send syscall instead of get them from f_creds.
Another potential user of netlink socket is task_diag, a faster /proc/PID-like interface proposed some time ago (https://lkml.org/lkml/2015/7/6/142). It makes sense to use the netlink interface for it, too, but the whole feature is currently blocked by the netlink discussion.
Tags
netlink, upai
Presentation Materials
slidesSpeaker
-
- Website: http://criu.org/
- Favorites: View Andrei's favorites
Biography
Developer in the CRIU and OpenVZ projects.
Andrew Vagin is interested in Container Virtualization (LXC, OpenVZ). He started to write autotest for OpenVZ in 2006, when he was a student at the Moscow Institute of Physics and Technology (MIPT). Now Andrew works in OpenVZ kernel team. In addition he is an active developer in the CRIU (Checkpoint/Restore in Userspace) project.