linux-ext4 - Re: ext4 compile error on m68k

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] [day] [month] [year] [list]

Message-ID: <20080410140142.GA18896@infradead.org>
Date:	Thu, 10 Apr 2008 10:01:42 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	Andreas Schwab <schwab@...e.de>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Adrian Bunk <bunk@...nel.org>, sct@...hat.com,
	akpm@...ux-foundation.org, adilger@...sterfs.com,
	zippel@...ux-m68k.org, linux-ext4@...r.kernel.org,
	linux-m68k@...r.kernel.org
Subject: Re: ext4 compile error on m68k

> Should be same  ext2_find_next_zero_bit except that it find the next
> set bit rather than the zero bit. The API is used to find the set bit
> in bitmap. To explain the little endian dependency, what we have is
> 
> 0	x	n
> [.......1.......]
> 
> Now we read this as (char *) and try to find the first set bit which
> in the above example is x. To speed up most of the architectures would
> like to consider it as an array of long. That implies that the value
> in the array should be considered as a little endian long, hence the
> *_le_bit.

This kind of documentation should be in the kernel tree somewhere.
And while we're at it all the routines should be renamed from extN_*
to *_le_bit because that describes what they do.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html