summaryrefslogtreecommitdiffhomepage
path: root/docs/xml/nginx/changes.xml
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
commita8bc01b466e3edec205ec4ecc5d0b2b6a172c9a2 (patch)
treef1c1b128837064427cbaa8661d1d04b41fb7971a /docs/xml/nginx/changes.xml
parent3a8727888262bf6da84b1df155909e424bbb3b30 (diff)
downloadnginx-a8bc01b466e3edec205ec4ecc5d0b2b6a172c9a2.tar.gz
nginx-a8bc01b466e3edec205ec4ecc5d0b2b6a172c9a2.tar.bz2
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 'docs/xml/nginx/changes.xml')
0 files changed, 0 insertions, 0 deletions