xfs-masters
[Top] [All Lists]

Re: [xfs-masters] [PATCH -next] xfs: eliminate kconfig dependency warnin

To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [xfs-masters] [PATCH -next] xfs: eliminate kconfig dependency warning
From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Date: Thu, 14 Oct 2010 10:18:19 -0700
Cc: xfs-masters@xxxxxxxxxxx, lkml <linux-kernel@xxxxxxxxxxxxxxx>, akpm <akpm@xxxxxxxxxxxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>
In-reply-to: <20101014092503.GA28446@xxxxxx>
Organization: Oracle Linux Engineering
References: <20101013210142.9d524535.randy.dunlap@xxxxxxxxxx> <20101014092503.GA28446@xxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-3.fc11 Thunderbird/3.0
On 10/14/10 02:25, Christoph Hellwig wrote:
> On Wed, Oct 13, 2010 at 09:01:42PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
>>
>> Fix kconfig dependency warning to satisfy dependencies:
>>
>> warning: (XFS_FS && BLOCK || NFSD && NETWORK_FILESYSTEMS && INET && 
>> FILE_LOCKING && BKL) selects EXPORTFS which has unmet direct dependencies 
>> (NETWORK_FILESYSTEMS)
> 
> I'm not entirely sure what this gibberish means, but I'm pretty sure it
> does not make sense.
> 
> EXPORTFS is a small module that doesn't have any dependencie, and it's
> needed by XFS for the by-handle operation, and by nfsd for the same
> thing.  It has absolutely nothing to do with networking or network
> filesystems (as in network filesystem clients).

The (kconfig) warning/problem is that exportfs is in the Networking Filesystems 
menu,
under the kconfig symbol NETWORK_FILESYSTEMS.

Dave Chinner wrote:
| EXPORTFS functionality actually has use for local filesystems - the
| open-by-handle interfaces in XFS are what uses it, and there are patches
| about that make this generic for most filesystems. Hence it seems to
| me that the correct thing to do is separate EXPORTFS from
| NETWORK_FILESYSTEMS, not make local filesystems depend on a user
| selecting network filesystem support....

Agreed.  Is that Kconfig change also part of the "patches about"?

thanks,
-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

<Prev in Thread] Current Thread [Next in Thread>