linux-kernel - Re: linux-next: next-20101022 broken with unset CONFIG

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:	Fri, 22 Oct 2010 11:30:17 +0200
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, sfr@...b.auug.org.au,
	Jan Harkes <jaharkes@...cmu.edu>
Subject: Re: linux-next: next-20101022 broken with unset CONFIG_BKL

On Fri, Oct 22, 2010 at 11:24 AM, Arnd Bergmann <arnd@...db.de> wrote:
> On Friday 22 October 2010 11:13:23 Sedat Dilek wrote:
>> Hi,
>>
>> I am trying to compile latest linux-next with unset CONFIG_BKL.
>> Yes, one patch is missing from [1] to be able to compile a BKL-free kernel.
>> (BTW, the patch needs a trivial fix, see v2 attached to this email.)
>>
>> With next-20101022 the build breaks (sorry for the output in German):
>>
>> [ build.log ]
>> ...
>>   LD [M]  fs/ceph/ceph.o
>>   LD      fs/coda/built-in.o
>>   CC [M]  fs/coda/psdev.o
>>   CC [M]  fs/cifs/misc.o
>> /home/sd/src/linux-2.6/linux-2.6.36/debian/build/source_i386_none/fs/coda/psdev.c:
>> In function ‘coda_psdev_write’:
>> /home/sd/src/linux-2.6/linux-2.6.36/debian/build/source_i386_none/fs/coda/psdev.c:140:
>> error: implicit declaration of function ‘lock_kernel’
>> /home/sd/src/linux-2.6/linux-2.6.36/debian/build/source_i386_none/fs/coda/psdev.c:142:
>> error: implicit declaration of function ‘unlock_kernel’
>>   CC      block/blk-settings.o
>> make[6]: *** [fs/coda/psdev.o] Fehler 1
>> make[5]: *** [fs/coda] Fehler 2
>> make[5]: *** Warte auf noch nicht beendete Prozesse...
>> ...
>>
>> Just FYI.
>>
>
> Ok, thanks for the report. There is a patch for coda to remove the BKL.
> We discussed it yesterday and I subsequently removed the switch that
> disables it on non-BKL configs.
>
> We then agreed to not have the patch included in my series, and Jan's
> tree is not part of linux-next.
>
> There are more of these in mainline once Linus pulls my tree, but that
> just means that we need to get all the other trees into -rc1 that
> remove the BKL from other subsystems, before applying the patch that
> lets you build with CONFIG_FILE_LOCKING=y and CONFIG_BKL=n.
>
> Right now, both allyesconfig (with BKL) and allnoconfig (without coda)
> work fine, we only get a few really obscure randconfigs breaking.
>
>        Arnd
>

Wow, you answer in realtime :-), Arnd.
Thanks for the explanations and I agree with you to wait for 27-rc1
and then to remove BKL.
Me just doing early-testing...

A pointer to the patch?
Thanks in advance.

- Sedat -
--
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/