[pnfs] 2.6.17 pnfs as client module

[Iyer, Rahul]

I don't believe the pnfs layoutdriver modules require it, but the nfs
module seems to require it. It uses it in recall_layout_thread() in
fs/nfs/delegation.c in order answer LAYOUTRECALLs. And since the nfs
module now depends on inode_lock, it fails to insert. And because the
pnfs layoutdriver module depends on the nfs module, it doesn't insert...

Regards
Rahul


-----Original Message-----
From: J. Bruce Fields [mailto:bfields at fieldses.org] 
Sent: Friday, July 28, 2006 11:59 AM
To: Iyer, Rahul
Cc: Dean Hildebrand; pnfs at linux-nfs.org
Subject: Re: [pnfs] 2.6.17 pnfs as client module

On Fri, Jul 28, 2006 at 11:53:11AM -0700, Iyer, Rahul wrote:
> Yep! I just tried it and ran into the very same thing. It works if 
> compiled into the kernel. I was going to bring this up.. the problem 
> AFAIK is that inode_lock doesn't have an EXPORT_SYMBOL(). It's defined

> in fs/inode.c, line 82.

Do you really need the inode_lock?

--b.