Skip site navigation (1) Skip section navigation (2)

unsafe use of hash_search(... HASH_ENTER ...)

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: unsafe use of hash_search(... HASH_ENTER ...)
Date: 2005-05-27 03:27:15
Message-ID: d7646e$lqi$ (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
-- First part ---

In md.c/RememberFsyncRequest():

 if (hash_search(pendingOpsTable, &entry, HASH_ENTER, NULL) == NULL)
     errmsg("out of memory")));

pendingOpsTable uses "MdCxt" to allocate memory. So if "out of memory", we
actually have no chance to raise the error level to FATAL. A quick fix is to
use malloc() HASH_ALLOC method for pendingOpsTable.

In general, code snippet like this:

if (hash_search(..., HASH_ENTER, ...) == NULL)

are considered unsafe if: (1) the allocation method of the target hash table
could elog(ERROR) themselves and (2) the reaction to the failure of
hash_search() is not elog(ERROR).

So shared memory hash table is safe because of condition (1). I scratched
the server code and find the following places are like this:

* RememberFsyncRequest() - solution as above;
* XLogOpenRelation() - not a problem, since it is already in the critical
* IndexNext() in 8.0.1;

-- Second part ---

Also, per discussion with Neil and Tom, it is possible to simplify code
snippets like this:

    if (hash_search(local_hash, HASH_ENTER, ...) == NULL)
        elog(ERROR, "out of memory");


    hash_search(local_hash, HASH_ENTER, ...);




pgsql-hackers by date

Next:From: Tom LaneDate: 2005-05-27 03:40:13
Subject: Re: unsafe use of hash_search(... HASH_ENTER ...)
Previous:From: Qingqing ZhouDate: 2005-05-27 03:22:10
Subject: Re: Can we simplify win32 threading code

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group