Hello.
I'd really appreciate for any comments on subj - implementation of new system
call: connectat and bindat.
Reasons for new system calls:
1) Path length for UNIX sockets is limited to 108 symbols.
Syscalls are useful as is since removes limitation.
2) Ability to perform connect/bind calls to UNIX sockets starting from specified
path in kernel.
This is required for proper support of kernel connect operations in SUNRPC
layer. Which, in turn, required for proper support of NFS in containers.
These system calls could be used only for non-abstract UNIX sockets, obviously.
Possible implementation could be adding of struct path pointer to sockaddr_un.
But this pointer have to valid only for connect and bind calls, and caller have
to hold and release path by himself.
--
Best regards,
Stanislav Kinsbursky
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
