From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: [PATCH 1/4] ore: FIX breakage when MISC_FILESYSTEMS is not set Date: Sat, 07 Jan 2012 10:19:38 -0800 Message-ID: <4F088CBA.1020105@xenotime.net> References: <4F070722.8030907@panasas.com> <4F0707FB.2070600@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: linux-fsdevel , open-osd , Stable Tree To: Boaz Harrosh Return-path: Received: from oproxy9.bluehost.com ([69.89.24.6]:58300 "HELO oproxy9.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752507Ab2AGRVP (ORCPT ); Sat, 7 Jan 2012 12:21:15 -0500 In-Reply-To: <4F0707FB.2070600@panasas.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 01/06/2012 06:40 AM, Boaz Harrosh wrote: > > As Reported by Randy Dunlap > > When MISC_FILESYSTEMS is not enabled and NFS4.1 is: > > fs/built-in.o: In function `objio_alloc_io_state': > objio_osd.c:(.text+0xcb525): undefined reference to `ore_get_rw_state' > fs/built-in.o: In function `_write_done': > objio_osd.c:(.text+0xcb58d): undefined reference to `ore_check_io' > fs/built-in.o: In function `_read_done': > ... > > When MISC_FILESYSTEMS, which is more of a GUI thing then anything else, > is not selected. exofs/Kconfig is never examined during Kconfig, > and it can not do it's magic stuff to automatically select everything > needed. > > We must split exofs/Kconfig in two. The ore one is always included. > And the exofs one is left in it's old place in the menu. > > [Needed for the 3.2.0 Kernel] > CC: Stable Tree > Reported-by: Randy Dunlap > Signed-off-by: Boaz Harrosh Acked-by: Randy Dunlap Thanks. > --- > fs/Kconfig | 2 ++ > fs/exofs/Kconfig | 11 ----------- > fs/exofs/Kconfig.ore | 12 ++++++++++++ > 3 files changed, 14 insertions(+), 11 deletions(-) > create mode 100644 fs/exofs/Kconfig.ore > > diff --git a/fs/Kconfig b/fs/Kconfig > index 5f4c45d..6ad58a5 100644 > --- a/fs/Kconfig > +++ b/fs/Kconfig > @@ -218,6 +218,8 @@ source "fs/exofs/Kconfig" > > endif # MISC_FILESYSTEMS > > +source "fs/exofs/Kconfig.ore" > + > menuconfig NETWORK_FILESYSTEMS > bool "Network File Systems" > default y > diff --git a/fs/exofs/Kconfig b/fs/exofs/Kconfig > index da42f32..86194b2 100644 > --- a/fs/exofs/Kconfig > +++ b/fs/exofs/Kconfig > @@ -1,14 +1,3 @@ > -# Note ORE needs to "select ASYNC_XOR". So Not to force multiple selects > -# for every ORE user we do it like this. Any user should add itself here > -# at the "depends on EXOFS_FS || ..." with an ||. The dependencies are > -# selected here, and we default to "ON". So in effect it is like been > -# selected by any of the users. > -config ORE > - tristate > - depends on EXOFS_FS || PNFS_OBJLAYOUT > - select ASYNC_XOR > - default SCSI_OSD_ULD > - > config EXOFS_FS > tristate "exofs: OSD based file system support" > depends on SCSI_OSD_ULD > diff --git a/fs/exofs/Kconfig.ore b/fs/exofs/Kconfig.ore > new file mode 100644 > index 0000000..1ca7fb7 > --- /dev/null > +++ b/fs/exofs/Kconfig.ore > @@ -0,0 +1,12 @@ > +# ORE - Objects Raid Engine (libore.ko) > +# > +# Note ORE needs to "select ASYNC_XOR". So Not to force multiple selects > +# for every ORE user we do it like this. Any user should add itself here > +# at the "depends on EXOFS_FS || ..." with an ||. The dependencies are > +# selected here, and we default to "ON". So in effect it is like been > +# selected by any of the users. > +config ORE > + tristate > + depends on EXOFS_FS || PNFS_OBJLAYOUT > + select ASYNC_XOR > + default SCSI_OSD_ULD -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***