linux-kernel - Re: [PATCH] udf: use ext2_find_next

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: <961aa3351002250629p11fc4a49m60aadbf79fc10696@mail.gmail.com>
Date:	Thu, 25 Feb 2010 23:29:14 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org,
	Linux-Next <linux-next@...r.kernel.org>
Subject: Re: [PATCH] udf: use ext2_find_next_bit

2010/2/25 Geert Uytterhoeven <geert@...ux-m68k.org>:
> On Thu, Feb 25, 2010 at 02:38, Akinobu Mita <akinobu.mita@...il.com> wrote:
>> 2010/2/25 Jan Kara <jack@...e.cz>:
>>> On Tue 23-02-10 23:11:13, Akinobu Mita wrote:
>>>> Use ext2_find_next_bit (generic_find_next_le_bit) to find the set bit
>>>> in little endian bitmap region.
>
> Is any of this in linux-next now?
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/2208481/
> | fs/udf/balloc.c:274: error: implicit declaration of function
> 'generic_find_next_le_bit'

Yep, Jan's patch caused the build breakage.

Because generic_find_next_le_bit() is not available for all
archtectures. So we should use ext2_find_next_bit() here.
--
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/