linux-kernel - Re: [PATCH -mmotm] nfs/cache_lib: fix sunrpc struct build error

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, 21 Aug 2009 13:51:12 -0400
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH -mmotm] nfs/cache_lib: fix sunrpc struct build error

On Fri, 2009-08-21 at 09:57 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@...cle.com>
> 
> Add header file for struct delayed_work:
> 
> In file included from fs/nfs/cache_lib.c:14:
> include/linux/sunrpc/rpc_pipe_fs.h:35: error: field 'queue_timeout' has incomplete type
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> ---
>  include/linux/sunrpc/rpc_pipe_fs.h |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- mmotm-2009-0820-1918.orig/include/linux/sunrpc/rpc_pipe_fs.h
> +++ mmotm-2009-0820-1918/include/linux/sunrpc/rpc_pipe_fs.h
> @@ -3,6 +3,8 @@
>  
>  #ifdef __KERNEL__
>  
> +#include <linux/workqueue.h>
> +
>  struct rpc_pipe_msg {
>  	struct list_head list;
>  	void *data;

Thanks Randy! Bruce Fields beat you to this bug by a few hours, so I've
already applied his fix. It should hit linux-next et al today.

Cheers
  Trond

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@...app.com
www.netapp.com
--
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/