linux-kernel - Re: [PATCH 22/22] bitops: remove minix bitops from asm/bitops.h

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]

Date:	Sat, 16 Oct 2010 21:40:03 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Andreas Schwab <schwab@...ux-m68k.org>,
	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Linux/m68k" <linux-m68k@...r.kernel.org>
Subject: Re: [PATCH 22/22] bitops: remove minix bitops from asm/bitops.h

2010/10/16 Geert Uytterhoeven <geert@...ux-m68k.org>:
> On Sat, Oct 16, 2010 at 10:50, Andreas Schwab <schwab@...ux-m68k.org> wrote:
>> Geert Uytterhoeven <geert@...ux-m68k.org> writes:
>>
>>> Funny, m68k uses the little endian minix file system?
>>>
>>> Perhaps this was due to minix using the ext2 accessors? And ext2 being
>>> switched from big to little endian ext2 on m68k, without anyone
>>> noticing the impact
>>> on minix?
>>
>> m68k has always used big-endian minixfs and the minix bitops were always
>> independent of the ext2 ones.
>
> Thanks for confirming!

m68knommu is big-endian minixfs but m68k (mmu) is little-endian minixfs
if I read arch/m68k/include/asm/bitops_{mm,no}.h correctly.
--
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/