summaryrefslogtreecommitdiffstats
path: root/drivers/input
diff options
context:
space:
mode:
authorPavel Emelyanov <xemul@parallels.com>2013-08-21 14:31:38 +0400
committerDavid S. Miller <davem@davemloft.net>2013-08-21 12:21:45 -0700
commitfb7589a162162223e6bb6422dde3fb1ce07d9a78 (patch)
treef99c3c7c9af2681f57b8b7beb4b859bf9d2bf4f5 /drivers/input
parent5f1cd200c4e4e1a6bce946aaac40c7a10427f3ed (diff)
downloadop-kernel-dev-fb7589a162162223e6bb6422dde3fb1ce07d9a78.zip
op-kernel-dev-fb7589a162162223e6bb6422dde3fb1ce07d9a78.tar.gz
tun: Add ability to create tun device with given index
Tun devices cannot be created with ifidex user wants, but it's required by checkpoint-restore project. Long time ago such ability was implemented for rtnl_ops-based interface for creating links (9c7dafbf net: Allow to create links with given ifindex), but the only API for creating and managing tuntap devices is ioctl-based and is evolving with adding new ones (cde8b15f tuntap: add ioctl to attach or detach a file form tuntap device). Following that trend, here's how a new ioctl that sets the ifindex for device, that _will_ be created by TUNSETIFF ioctl looks like. So those who want a tuntap device with the ifindex N, should open the tun device, call ioctl(fd, TUNSETIFINDEX, &N), then call TUNSETIFF. If the index N is busy, then the register_netdev will find this out and the ioctl would be failed with -EBUSY. If setifindex is not called, then it will be generated as before. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/input')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud