You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/09/27 07:43:04 UTC

[jira] [Updated] (TS-3949) Active timeout event on PluginVC may fire after it's already closed.

     [ https://issues.apache.org/jira/browse/TS-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudheer Vinukonda updated TS-3949:
----------------------------------
         Assignee: Sudheer Vinukonda
    Fix Version/s: 6.1.0

> Active timeout event on PluginVC may fire after it's already closed.
> --------------------------------------------------------------------
>
>                 Key: TS-3949
>                 URL: https://issues.apache.org/jira/browse/TS-3949
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, Plugins
>            Reporter: Sudheer Vinukonda
>            Assignee: Sudheer Vinukonda
>             Fix For: 6.1.0
>
>
> When a plugin sets TS_EVENT_VCONN_ACTIVE_TIMEOUT on Plugin VC, it looks like, in some race conditions, the active timer event could still get fired after the Plugin VC is already closed, leading INKContInternal::handle_event to assert a use-after-free.
> Note: The plugin VC's process_close does cancel the active timeout event, so, this doesn't happen every time. It might happen in some race conditions or when the timeout and close are on different threads (?)..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)