From: Arnd Bergmann <arnd@arndb.de>
To: sedat.dilek@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au, Jan Harkes <jaharkes@cs.cmu.edu>
Subject: Re: linux-next: next-20101022 broken with unset CONFIG_BKL
Date: Fri, 22 Oct 2010 11:24:32 +0200 [thread overview]
Message-ID: <201010221124.32842.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTi=vUA-u20egbpH1Wu4ek-craz7aZUxWmobL8OhD@mail.gmail.com>
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
next prev parent reply other threads:[~2010-10-22 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:13 linux-next: next-20101022 broken with unset CONFIG_BKL Sedat Dilek
2010-10-22 9:24 ` Arnd Bergmann [this message]
2010-10-22 9:30 ` Sedat Dilek
2010-10-22 9:36 ` Arnd Bergmann
2010-10-22 11:34 ` Sedat Dilek
2010-10-22 16:03 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010221124.32842.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox