[quic] ngx_quic_input_handler Segmentation fault because c->udp->dgram is null

Gao,Yan(媒体云) gaoyan09 at baidu.com
Fri Jan 28 03:29:06 UTC 2022

> first time you get there with main nginx connection, when a first QUIC
> packet arrives. Thus test c->quic. and if it is NULL it means we need
> to create main quic connection and proceed with the handshake.

> When the handshake is complete, a stream will be created, and the
> ngx_quic_init_stream_handler() will be called which will invoke
> listening handler, and we will return into ngx_http_v3_init() with
> stream connection that has c->quic set and follow the other path.

Yes, I understand. But what you said, as stream connection that has c->quic set, when main nginx connection c->quic set?
ngx_ssl_shutdown and ngx_http_v3_init check c->quic == NULL, but it is never set.
No problem?

Gao,Yan(ACG VCP)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20220128/9754af75/attachment.htm>

More information about the nginx-devel mailing list