mirror of
https://github.com/samba-team/samba.git
synced 2025-01-11 05:18:09 +03:00
smbd: explain that/why we use the raw tevent_context for update_write_time_handler()
Signed-off-by: Stefan Metzmacher <metze@samba.org> Reviewed-by: Ralph Boehme <slow@samba.org>
This commit is contained in:
parent
b0af5715b0
commit
7cfafaf190
@ -232,9 +232,17 @@ void trigger_write_time_update(struct files_struct *fsp)
|
||||
DEBUG(5, ("Update write time %d usec later on %s\n",
|
||||
delay, fsp_str_dbg(fsp)));
|
||||
|
||||
/* trigger the update 2 seconds later */
|
||||
/*
|
||||
* trigger the update 2 seconds later
|
||||
*
|
||||
* Note that update_write_time_handler()
|
||||
* => fsp_flush_write_time_update()
|
||||
* won't do any SMB_VFS calls and don't
|
||||
* need impersonation. So we use the
|
||||
* raw event context for this.
|
||||
*/
|
||||
fsp->update_write_time_event =
|
||||
tevent_add_timer(fsp->conn->sconn->ev_ctx, NULL,
|
||||
tevent_add_timer(fsp->conn->sconn->raw_ev_ctx, NULL,
|
||||
timeval_current_ofs_usec(delay),
|
||||
update_write_time_handler, fsp);
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user