Mercurial > hg > nginx-quic
view src/core/ngx_syslog.h @ 6673:e4c1f5b32868
Event pipe: do not set file's thread_handler if not needed.
This fixes a problem with aio threads and sendfile with aio_write switched
off, as observed with range requests after fc72784b1f52 (1.9.13). Potential
problems with sendfile in threads were previously described in 9fd738b85fad,
and this seems to be one of them.
The problem occurred as file's thread_handler was set to NULL by event pipe
code after a sendfile thread task was scheduled. As a result, no sendfile
completion code was executed, and the same buffer was additionally sent
using non-threaded sendfile. Fix is to avoid modifying file's thread_handler
if aio_write is switched off.
Note that with "aio_write on" it is still possible that sendfile will use
thread_handler as set by event pipe. This is believed to be safe though,
as handlers used are compatible.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Thu, 01 Sep 2016 20:05:23 +0300 |
parents | a6a2016b8e31 |
children | 7f9935f07fe9 |
line wrap: on
line source
/* * Copyright (C) Nginx, Inc. */ #ifndef _NGX_SYSLOG_H_INCLUDED_ #define _NGX_SYSLOG_H_INCLUDED_ typedef struct { ngx_pool_t *pool; ngx_uint_t facility; ngx_uint_t severity; ngx_str_t tag; ngx_addr_t server; ngx_connection_t conn; unsigned busy:1; unsigned nohostname:1; } ngx_syslog_peer_t; char *ngx_syslog_process_conf(ngx_conf_t *cf, ngx_syslog_peer_t *peer); u_char *ngx_syslog_add_header(ngx_syslog_peer_t *peer, u_char *buf); void ngx_syslog_writer(ngx_log_t *log, ngx_uint_t level, u_char *buf, size_t len); ssize_t ngx_syslog_send(ngx_syslog_peer_t *peer, u_char *buf, size_t len); #endif /* _NGX_SYSLOG_H_INCLUDED_ */