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:	Tue, 3 May 2011 17:11:20 +0800
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Greg Ungerer <gerg@...pgear.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	akpm@...ux-foundation.org, arnd@...db.de,
	Greg Ungerer <gerg@...inux.org>, geert@...ux-m68k.org
Subject: Re: [PATCH v3 1/7] m68knommu: fix build error due to the lack of find_next_bit_le()

2011/5/3, Greg Ungerer <gerg@...pgear.com>:
> Hi Akinobu,
>
> On 27/04/11 23:20, Akinobu Mita wrote:
>> m68knommu can't build ext4, udf, and ocfs2 due to the lack of
>> find_next_bit_le().
>>
>> This implements find_next_bit_le() on m68knommu by duplicating the
>> generic find_next_bit_le() in lib/find_next_bit.c.
>
> Wouldn't the m68k specific implementation of this in
> arch/m68k/include/asm/bitops_mm.h be better?

find_next_bit_le() in bitops_mm.h has a bug
(Please see https://lkml.org/lkml/2011/4/3/43) and it is not fixed
in mainline yet. So I decided to use generic one for the safety.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ