Bug 184588 - db_185 btree API returns key sizes with high bits set to garbage
Summary: db_185 btree API returns key sizes with high bits set to garbage
Alias: None
Product: Fedora
Classification: Fedora
Component: db4
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-10 01:05 UTC by Henrik Nordstrom
Modified: 2013-07-02 23:15 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-03-13 16:53:16 UTC

Attachments (Terms of Use)
test_db.c (796 bytes, text/plain)
2006-03-10 01:05 UTC, Henrik Nordstrom
no flags Details
Change compare and prefix functions to use DBT185 wrapper (1.75 KB, patch)
2006-03-13 15:51 UTC, Henrik Nordstrom
no flags Details | Diff
Change compare and prefix functions to use DBT185 wrapper (1.75 KB, patch)
2006-03-13 16:17 UTC, Henrik Nordstrom
no flags Details | Diff

Description Henrik Nordstrom 2006-03-10 01:05:06 UTC
Description of problem:

the compare function in db_185 mode is called with key2 containing garbage in
the high bits of the size field.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. gcc -o test_db test_db.c -ldb
2. ./test_db
Actual results:

key1->size = 3
key2->size = 2ada00000003

Expected results:

key1->size = 3
key2->size = 3

Additional info:

Comment 1 Henrik Nordstrom 2006-03-10 01:05:07 UTC
Created attachment 125913 [details]

Comment 2 Jindrich Novy 2006-03-10 12:37:16 UTC
Yes, reproduced on x86_64.

  key->size should be cast as size_t instead of unsigned long.

Comment 3 Henrik Nordstrom 2006-03-11 22:30:59 UTC
size_t isn't known to printf.. unsigned long is the closest approximation which
is.. (key->size is a size_t).

Either way the problem is not related to the cast. The cast is just there to be
able to print this size_t. 

Comment 4 Jindrich Novy 2006-03-13 15:17:52 UTC
Of course it's not a cast problem, but a db bug.

The problem is that __bam_cmp() from bt_compare.c that calls compare() function
in your code actually calls the comparison function prototyped as:

int (*func)__P((DB *, const DBT *, const DBT *));

but the prototype declared in BTREEINFO claims the comparison function is:

        int     (*compare)      /* comparison function */
            __P((const DBT *, const DBT *));

what doesn't look too consistent to me.

Comment 5 Henrik Nordstrom 2006-03-13 15:32:00 UTC
I seriously doubt this is the case. If this was the case then the compare
function would not work at all, and the first argument surely would not be the
needle to match against.

Now the first argument works fine, and is the needle to match agains. The
problem is in the second argument where dbt->data is correct but dbt->size
contains garbage in the high bits and the correct size in the lower 32 bits.

From what I can tell func mentioned here should be db185_compare, which in turn
talls the supplied compare function with the correct arguments.

Comment 6 Henrik Nordstrom 2006-03-13 15:47:23 UTC
Looked a bit further. The problem is in db185/ where DBT is used for the 185
compare function where DBT185 should be used..  db185_compare should in fact
translate DBT to DBT185, not pass it along unmodified. Works on 32-bit machines
only because there DBT and DBT185 has the exact same common fields with DBT only
beeing bigger (size_t == uint32_t on 32-bits), but fails on 64-bit machines as
there size_t is 64 bits while DBT only has 32-bits in the size field.. 

The "garbage" is the ulen field from the DB4 DBT incorrectly passed to the
compare function..

Comment 7 Henrik Nordstrom 2006-03-13 15:51:30 UTC
Created attachment 126044 [details]
Change compare and prefix functions to use DBT185 wrapper

Attached is an initial patch adding this translation of DBT to DBT185. Not yet
verified, but should work...

Note: DBT185 is the internal representation of the 1.85 DBT, same as DBT in

Comment 8 Henrik Nordstrom 2006-03-13 16:08:05 UTC
Looked into upstream release notes and it's a known bug in 4.3.29 and is fixed
in 4.4.20. Documented in the "Utility Changes" section of the release notes.

     3.     Fix a bug in the 1.85 compatibility code supporting
     per-application Btree comparison and prefix compression functions.
     The functions would not work on big-endian 64-bit hardware. [#13316]

just that the bug is broader than they thought and it these functions won't work
on 64-bit hardware, little or big endian.

Comment 9 Henrik Nordstrom 2006-03-13 16:17:54 UTC
Created attachment 126050 [details]
Change compare and prefix functions to use DBT185 wrapper

Sorry, got the patch order reversed in the original patch. This is the same
patch but in correct direction..

the building of a patched db4 package has now finished and the patch has now
been verified to do what it should..

Comment 10 Henrik Nordstrom 2006-03-13 16:23:56 UTC
One more note: The DB man page documents db 1.85, not the DB 2.X or later

should file a bug against the man-pages package about the header name in the man
page, still claims one should include db.h when the db 1.85 API is in db_185.h..

Comment 11 Jindrich Novy 2006-03-13 16:53:16 UTC
Yes, feel free to report a new bug for man pages then. I do believe that
documentation might be outdated.

Your fix is now applied. Thanks.

Comment 12 Fedora Update System 2006-03-14 17:19:41 UTC
From User-Agent: XML-RPC

db4-4.3.27-5.fc4 has been pushed for FC4, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 13 Henrik Nordstrom 2006-03-17 22:40:00 UTC
Haven't seen an FC5 update of this package yet. Seems a bit odd to have it
pushed to FC4, but not FC5 which the bug was reported against.

If it is in the FC5 repository but just not yet rebuilt / propagated out to the
mirrors then ignore me. If not please don't forget to push it into FC5 as well
at some point in time..

Comment 14 Jindrich Novy 2006-03-18 09:12:40 UTC
The delay is caused by FC5/FC6 branch split done yestreday, which of course
doesn't affect FC4, therefore it's pushed sooner. FC5 db4 is now built for four
days already so the package will appear in FC5 updates soon.

Note You need to log in before you can comment on or make changes to this bug.