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

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: <20081031073507.GB18182@logfs.org>
Date:	Fri, 31 Oct 2008 08:35:07 +0100
From:	Jörn Engel <joern@...fs.org>
To:	Christian Borntraeger <borntraeger@...ibm.com>
Cc:	Pavel Machek <pavel@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] B+Tree library

On Fri, 31 October 2008 07:38:46 +0100, Christian Borntraeger wrote:
> Am Donnerstag, 30. Oktober 2008 schrieb Jörn Engel:
> > Except that min/max in include/linux/kernel.h have some type-safety
> > added.  In this particular case that is actually a disadvantage:
> 
> So what about min_t and max_t from include/linux/kernel.h? Can that be used?

Sorry, no.  The problems comes from using MAX in structure initializers.

struct btree_geo btree_geo32 = {
	.keylen = 1,
	.no_pairs = NODESIZE / sizeof(long) / 2,
};

Jörn

-- 
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is easily forgotten.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/