projects / haproxy-2.3.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1553b66) | patch
MINOR: mux-h1: avoid taking the toremove_lock in on dying tasks
authorWilly Tarreau <w@1wt.eu>
Tue, 30 Jun 2020 09:19:23 +0000 (11:19 +0200)
committerWilly Tarreau <w@1wt.eu>
Tue, 30 Jun 2020 12:06:19 +0000 (14:06 +0200)
commit68d4ee9e261e6a6a921e2107b43a36ed5299e8f3
tree267a8b6ea384b846bf0ba5eadd354d0e1e1bbeebtree | snapshot
parent1553b6657dd15565baaa0220ab232ba6c9cf7797commit | diff
MINOR: mux-h1: avoid taking the toremove_lock in on dying tasks

If the owning task is already dying (context was destroyed by h1_takeover)
there's no point taking the lock then removing it later since all the code
in between is conditionned by a non-null context. Let's simplify this.
src/mux_h1.c diff | blob | history
haproxy-2.3 public tree. Stable production code.