You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2010/02/12 00:20:28 UTC
[jira] Updated: (TS-170) hostdb cores in reply_to_cont() when
running out of space
[ https://issues.apache.org/jira/browse/TS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Call updated TS-170:
--------------------------
Attachment: hostdb_bcall_001.diff
Patch to check for NULL in reply_to_cont() and reducing the high water mark for the garbage collection from 90% to 80%.
> hostdb cores in reply_to_cont() when running out of space
> ---------------------------------------------------------
>
> Key: TS-170
> URL: https://issues.apache.org/jira/browse/TS-170
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Bryan Call
> Assignee: Bryan Call
> Fix For: 2.0.0a
>
> Attachments: hostdb_bcall_001.diff
>
>
> In HostDBContinuation::lookup_done() if we can't allocate memory in the cache we will free some space (delete_block())
> and then return a NULL. Also, the error message "out of room in hostdb for reverse DNS data" gets printed
> out.
> This NULL pointer will be dereferenced later when we call reply_to_cont().
> bz 3191464
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.