linux-kernel - Re: [RFC] B+Tree library V2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1231433404.8398.1.camel@johannes>
Date:	Thu, 08 Jan 2009 17:50:04 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Jörn Engel <joern@...fs.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] B+Tree library V2


> Maybe it should be renamed to btree_get_prev_key().  I never noticed how
> confusing it was because my head was busy with other problems.  The code
> is currently burried within my logfs tree:
> http://logfs.org/git?p=logfs;a=summary

I see this:


- * Second trick is to special-case the key "0" or NUL.  As seen above, this
- * value indicates an unused slot, so such a value should not be stored in the
- * tree itself.  Instead it is stored in the null_ptr field in the btree_head.

Does that mean that wasn't true, and I can store a 0 key?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)