ksmbd

[Luke Kenneth Casson Leighton]

> There is no select().  It registers with the TCP stack so when a packet
> arrives on port 139 one of the ksmbd threads is awakened and it starts
> processing it.  The thread figures out which session/user the packet is
> for by matching the kernel socket data structure with the look-aside
> structures.  This is especially easy since there is an opaque (to the
> socket) value that can be stored in the socket data structure.

guy,

we should do a gss_ntdom.  then you can associate not only a uid/gid but a
SID with the kernel process.