On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote: > On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin <avagin@xxxxxxxxxx> wrote: > > Currently we use the proc file system, where all information are > > presented in text files, what is convenient for humans. But if we need > > to get information about processes from code (e.g. in C), the procfs > > doesn't look so cool. > > > > From code we would prefer to get information in binary format and to be > > able to specify which information and for which tasks are required. Here > > is a new interface with all these features, which is called task_diag. > > In addition it's much faster than procfs. > > > > task_diag is based on netlink sockets and looks like socket-diag, which > > is used to get information about sockets. > > I think I like this in principle, but I have can see a few potential > problems with using netlink for this: > > 1. Netlink very naturally handles net namespaces, but it doesn't > naturally handle any other kind of namespace. In fact, the taskstats > code that you're building on has highly broken user and pid namespace > support. (Look for some obviously useless init_user_ns and > init_pid_ns references. But that's only the obvious problem. That > code calls current_user_ns() and task_active_pid_ns(current) from > .doit, which is, in turn, called from sys_write, and looking at > current's security state from sys_write is a big no-no.) > > You could partially fix it by looking at f_cred's namespaces, but that > would be a change of what it means to create a netlink socket, and I'm > not sure that's a good idea. If I don't miss something, all problems around pidns and userns are related with multicast functionality. task_diag is using request/response scheme and doesn't send multicast packets. > > 2. These look like generally useful interfaces, which means that > people might want to use them in common non-system software, which > means that some of that software might get run inside of sandboxes > (Sandstorm, xdg-app, etc.) Sandboxes like that might block netlink > outright, since it can't be usefully filtered by seccomp. (This isn't > really the case now, since netlink route queries are too common, but > still.) > > 3. Netlink is a bit tedious to use from userspace. Especially for > things like task_diag, which are really just queries that generate > single replies. I don't understand this point. Could you elaborate? I thought the netlink was designed for such purposes. (not only for them, but for them too) There are two features of netlink which are used. The netlink interface allows to split response into a few packets, if it's too big to be transferred for one iteration. And I want to mention "Memory mapped netlink I/O" functionality, which can be used to speed up task_diag. > > Would it make more sense to have a new syscall instead? You could > even still use nlattr formatting for the syscall results. Andy, thank you for the feedback. I got your points. I need time to think about them. I suppose that a new syscall can be more suitable in this case, and I need time to form a vision of it. If you have any ideas or thoughts, I would be glad to know about them. Thanks, Andrew > > --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
