[Pkg-db-devel] Bug#469602: libdb4.6: bug in memory pool set_maxsize() causes mutex deadlock

[Kevin Lindsay]

Package: libdb4.6
Severity: normal
Tags: patch

Currently it is not possible to set an in-memory database's maxium size using
it's memory pool's set_maxsize() function. Calling this function after a
db_open will cause libdb to hang in a mutex deadlock. This has only been
tested on an in-memory database using shared memory. The fix is a one liner
and seems to be pretty obvious. A patch is attached.

I have not yet reported this to upstream. Please let me know if you will be
doing this or if I can help out in anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: db-4.6.21-set-maxsize.patch
Type: text/x-diff
Size: 352 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-db-devel/attachments/20080305/1e1230ef/attachment.patch 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-db-devel/attachments/20080305/1e1230ef/attachment.pgp