aboutsummaryrefslogtreecommitdiff
path: root/m4/xc-am-iface.m4
diff options
context:
space:
mode:
authorDaniel Gustafsson <daniel@yesql.se>2019-06-24 23:30:31 +0200
committerDaniel Gustafsson <daniel@yesql.se>2019-06-24 23:35:06 +0200
commitb96282010e4b8bf373c1fb631a5e305442af634a (patch)
tree415c80403a79252d3cc6807c6fddfc649bc32ed8 /m4/xc-am-iface.m4
parent1853c884ef28197339e57f4ec405630944300855 (diff)
http: clarify header buffer size calculation
The header buffer size calculation can from static analysis seem to overlow as it performs an addition between two size_t variables and stores the result in a size_t variable. Overflow is however guarded against elsewhere since the input to the addition is regulated by the maximum read buffer size. Clarify this with a comment since the question was asked. Reviewed-by: Daniel Stenberg <daniel@haxx.se>
Diffstat (limited to 'm4/xc-am-iface.m4')
0 files changed, 0 insertions, 0 deletions