search for: vfs_fn_pointers

...st example1: parameter = 1 example: parameter = 5 test: parameter = 7 for example, when change the example1: parameter = 2, how to change or update the already constructed handler. ???: Liujun (A) ????: 2013?2?25? 20:59 ???: 'samba at lists.samba.org' ??: how to dynamic update or refresh vfs_fn_pointers and ntvfs_ops stacks When review vfs plugin architecture, the vfs hander or ntvfs hander is initial by tree connect, but when dynamic change the the share configure, how to change or update the already constructed handler .

...ot (by smb_vfs_call_copy_chunk_send). So I tried to return a failure in this function (-1 with errno=ENOENT). I saw that it indeed helps: Restore operation hits an error. But it takes about 10 seconds, until unmount of the snapshot finally succeeds. My question is: is there any other operation in “vfs_fn_pointers” that I can implement or fail to make vfs_shadow_copy2 quickly close all open file descriptors, such that unmount of the snapshot succeeds? Thanks, Alex. [1] vfs_shadow_copy2: add shadow_copy2_do_convert() [2] vfs_shadow_copy2: fix case where snapshots are outside the share

...chunk_send). So I tried to return a failure in this > function (-1 with errno=ENOENT). I saw that it indeed helps: Restore > operation hits an error. But it takes about 10 seconds, until unmount of the > snapshot finally succeeds. > > My question is: is there any other operation in “vfs_fn_pointers” that I can > implement or fail to make vfs_shadow_copy2 quickly close all open file > descriptors, such that unmount of the snapshot succeeds? > > Thanks, > Alex. Hmmm. Isn't this the equivalent of cancelling an async op in the middle of the operation ? That's notoriously...

...ried to return a failure in this >> function (-1 with errno=ENOENT). I saw that it indeed helps: Restore >> operation hits an error. But it takes about 10 seconds, until unmount of the >> snapshot finally succeeds. >> >> My question is: is there any other operation in “vfs_fn_pointers” that I >> can implement or fail to make vfs_shadow_copy2 quickly close all open file >> descriptors, such that unmount of the snapshot succeeds? >> >> Thanks, >> Alex. >> >> [1] >> vfs_shadow_copy2: add shadow_copy2_do_convert() >> [2] >>...

...ried to return a failure in this >> function (-1 with errno=ENOENT). I saw that it indeed helps: Restore >> operation hits an error. But it takes about 10 seconds, until unmount of the >> snapshot finally succeeds. >> >> My question is: is there any other operation in “vfs_fn_pointers” that I can >> implement or fail to make vfs_shadow_copy2 quickly close all open file >> descriptors, such that unmount of the snapshot succeeds? >> >> Thanks, >> Alex. > > Hmmm. Isn't this the equivalent of cancelling an async > op in the middle of the op...

...OP_NOOP = -1, ... /* File operations */ SMB_VFS_OP_OPEN, SMB_VFS_OP_CLOSE, SMB_VFS_OP_READ, SMB_VFS_OP_WRITE, SMB_VFS_OP_LSEEK, SMB_VFS_OP_SENDFILE, ... SMB_VFS_OP_LAST } vfs_op_type; This struct contains the function and handle pointers for all operations. struct vfs_ops { struct vfs_fn_pointers { ... /* File operations */ int (*open)(struct vfs_handle_struct *handle, struct connection_struct *conn, const char *fname, int flags, mode_t mode); int (*close)(struct vfs_handle_struct *handle, struct files_struct *fsp, int fd); ssize_t (*read)(struct vfs_handle_struct *hand...