Welcome! Log In Create A New Profile

Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5

Forum List Message List New Topic Print View

Yichun Zhang (agentzh)

October 01, 2014 03:38PM

Hello!

On Tue, Sep 30, 2014 at 5:36 PM, Maxim Dounin wrote:
>
> With such a change timer idents will become much less readable
> for connection-related timers (that is, most of them), so this
> is a last resort.
>

Yes, I know. Maybe let the caller explicitly tell ngx_event_t whether
ev->data is an ngx_connect_t pointer and just in this case, output the
fd in it?

Regards,
-agentzh

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel

Reply Quote

RSS

Subject	Author	Views	Posted
[BUG] New memory invalid read regression in resolver since nginx 1.7.5	Yichun Zhang (agentzh)	1269	September 30, 2014 06:12PM
Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5	Yichun Zhang (agentzh)	351	September 30, 2014 06:52PM
Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5	Maxim Dounin	362	September 30, 2014 08:38PM
Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5	Yichun Zhang (agentzh)	399	October 01, 2014 03:38PM
Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5	Maxim Dounin	395	September 30, 2014 08:34PM
Re: [BUG] New memory invalid read regression in resolver since nginx 1.7.5	Ruslan Ermilov	355	November 18, 2014 05:26AM

Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 278

Record Number of Users: 8 on April 13, 2023

Record Number of Guests: 421 on December 02, 2018