Mercurial > hg > nginx-quic
view src/os/unix/ngx_sunpro_sparc64.il @ 9049:a10210a45c8b
Core: stricter UTF-8 handling in ngx_utf8_decode().
An UTF-8 octet sequence cannot start with a 11111xxx byte (above 0xf8),
see https://datatracker.ietf.org/doc/html/rfc3629#section-3. Previously,
such bytes were accepted by ngx_utf8_decode() and misinterpreted as 11110xxx
bytes (as in a 4-byte sequence). While unlikely, this can potentially cause
issues.
Fix is to explicitly reject such bytes in ngx_utf8_decode().
author | Yugo Horie <u5.horie@gmail.com> |
---|---|
date | Thu, 23 Feb 2023 08:09:50 +0900 |
parents | d620f497c50f |
children |
line wrap: on
line source
/ / Copyright (C) Igor Sysoev / Copyright (C) Nginx, Inc. / / "casa [%o2] 0x80, %o1, %o0" and / "casxa [%o2] 0x80, %o1, %o0" do the following: / / if ([%o2] == %o1) { / swap(%o0, [%o2]); / } else { / %o0 = [%o2]; / } / ngx_atomic_uint_t ngx_casa(ngx_atomic_uint_t set, ngx_atomic_uint_t old, / ngx_atomic_t *lock); / / the arguments are passed in the %o0, %o1, %o2 / the result is returned in the %o0 .inline ngx_casa,0 casa [%o2] 0x80, %o1, %o0 .end / ngx_atomic_uint_t ngx_casxa(ngx_atomic_uint_t set, ngx_atomic_uint_t old, / ngx_atomic_t *lock); / / the arguments are passed in the %o0, %o1, %o2 / the result is returned in the %o0 .inline ngx_casxa,0 casxa [%o2] 0x80, %o1, %o0 .end