From: Dave Chinner <david@fromorbit.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: xfs-masters@oss.sgi.com, lkml <linux-kernel@vger.kernel.org>,
Alex Elder <aelder@sgi.com>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] xfs: eliminate kconfig dependency warning
Date: Thu, 14 Oct 2010 15:48:08 +1100 [thread overview]
Message-ID: <20101014044808.GB4681@dastard> (raw)
In-Reply-To: <20101013210142.9d524535.randy.dunlap@oracle.com>
On Wed, Oct 13, 2010 at 09:01:42PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> 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)
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> fs/xfs/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20101013.orig/fs/xfs/Kconfig
> +++ linux-next-20101013/fs/xfs/Kconfig
> @@ -1,6 +1,6 @@
> config XFS_FS
> tristate "XFS filesystem support"
> - depends on BLOCK
> + depends on BLOCK && NETWORK_FILESYSTEMS
> select EXPORTFS
> help
> XFS is a high performance journaling filesystem which originated
This looks wrong to me. IIUC, this means if you turn of network
filesystem support (e.g no NFS, CIFS, etc), you can't select XFS
even though it is a local filesystem.
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....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-10-14 4:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 4:01 [PATCH -next] xfs: eliminate kconfig dependency warning Randy Dunlap
2010-10-14 4:48 ` Dave Chinner [this message]
2010-10-14 9:25 ` [xfs-masters] " Christoph Hellwig
2010-10-14 15:44 ` Randy Dunlap
2010-10-14 17:18 ` Randy Dunlap
2010-10-14 20:55 ` Dave Chinner
2010-10-14 21:03 ` Randy Dunlap
2010-10-14 22:32 ` Christoph Hellwig
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=20101014044808.GB4681@dastard \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=xfs-masters@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.