| 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
| ||
|
Message-Id: <351E30A8-F8E2-4DD8-8AB1-52D1D397785D@fys.uio.no>
Date: Mon, 22 Mar 2010 05:49:40 -0400
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the nfs tree
On Mar 21, 2010, at 20:26, Stephen Rothwell <sfr@...b.auug.org.au>
wrote:
> Hi Trond,
>
> After merging the nfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/sunrpc/xprt.c: In function 'xprt_release':
> net/sunrpc/xprt.c:1045: error: implicit declaration of function
> 'xprt_free_bc_request'
>
> Caused by commit 0d28e05a53109bb52f254d5eac25dac6e3768b04 ("SUNRPC:
> Fix a
> use after free bug with the NFSv4.1 backchannel").
> xprt_free_bc_request()
> is only declared for CONFIG_NFS_V4_1 ...
>
> I have used the nfs tree from next-20100319 for today.
Hi Stephen
Sorry about that. I've got a fix for the above (just need to define
empty inline function for the !CONFIG_NFS_V4_1 case).
I'll try to upload it later today. (I am unfortunately travelling so
wifi access is a bit spotty).
Cheers
Trond
--
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