mirror of
https://github.com/samba-team/samba.git
synced 2024-12-25 23:21:54 +03:00
d380c49791
backend The vfs_unixuid module changes the uid of the process when executing operations on behalf of the user. Within the VFS backend we may rely on semi-async calls, such as winbind calls, which will call the event loop again. To cope with this we need to ensure that while inside those calls we revert the uid to root, then revert back to the connected user when we have finished with the semi-async calls. |
||
|---|---|---|
| .. | ||
| cifs | ||
| cifs_posix_cli | ||
| common | ||
| ipc | ||
| nbench | ||
| posix | ||
| simple | ||
| smb2 | ||
| sysdep | ||
| unixuid | ||
| config.mk | ||
| ntvfs_base.c | ||
| ntvfs_generic.c | ||
| ntvfs_interface.c | ||
| ntvfs_util.c | ||
| ntvfs.h | ||
| README | ||
This is the base of the new NTVFS subsystem for Samba. The model for NTVFS backends is quite different than for the older style VFS backends, in particular: - the NTVFS backends receive windows style file names, although they are in the unix charset (usually UTF8). This means the backend is responsible for mapping windows filename conventions to unix filename conventions if necessary - the NTVFS backends are responsible for changing effective UID before calling any OS local filesystem operations (if needed). The become_*() functions are provided to make this easier. - the NTVFS backends are responsible for resolving DFS paths - each NTVFS backend handles either disk, printer or IPC$ shares, rather than one backend handling all types - the entry points of the NTVFS backends correspond closely with basic SMB operations, wheres the old VFS was modelled directly on the POSIX filesystem interface. - the NTVFS backends are responsible for all semantic mappings, such as mapping dos file attributes, ACLs, file ownership and file times