aboutsummaryrefslogtreecommitdiff
path: root/src/http/ngx_http_request.c
diff options
context:
space:
mode:
authorMaxim Dounin <mdounin@mdounin.ru>2021-10-30 02:39:19 +0300
committerMaxim Dounin <mdounin@mdounin.ru>2021-10-30 02:39:19 +0300
commit2c8dd1c33e19842fcf1e87b53cb86aeeea094dda (patch)
tree410c73dc78269f3371d9bd67aee3bd5843bf0fcf /src/http/ngx_http_request.c
parent5636e7f7b491a4db287e3aa5312cd5955075f5ec (diff)
downloadnginx-2c8dd1c33e19842fcf1e87b53cb86aeeea094dda.tar.gz
nginx-2c8dd1c33e19842fcf1e87b53cb86aeeea094dda.zip
Changed ngx_chain_update_chains() to test tag first (ticket #2248).
Without this change, aio used with HTTP/2 can result in connection hang, as observed with "aio threads; aio_write on;" and proxying (ticket #2248). The problem is that HTTP/2 updates buffers outside of the output filters (notably, marks them as sent), and then posts a write event to call output filters. If a filter does not call the next one for some reason (for example, because of an AIO operation in progress), this might result in a state when the owner of a buffer already called ngx_chain_update_chains() and can reuse the buffer, while the same buffer is still sitting in the busy chain of some other filter. In the particular case a buffer was sitting in output chain's ctx->busy, and was reused by event pipe. Output chain's ctx->busy was permanently blocked by it, and this resulted in connection hang. Fix is to change ngx_chain_update_chains() to skip buffers from other modules unconditionally, without trying to wait for these buffers to become empty.
Diffstat (limited to 'src/http/ngx_http_request.c')
0 files changed, 0 insertions, 0 deletions