From: Chandra Seetharaman <sekharan@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, hare@suse.de,
scsi <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.26-rc2-mm1 (SCSI_DH build errors)
Date: Thu, 15 May 2008 12:56:14 -0700 [thread overview]
Message-ID: <1210881374.21974.285.camel@chandra-ubuntu> (raw)
In-Reply-To: <1210862779.15852.4.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
Hi James, Andrew,
Here is a patch to remove the automatic "select" of scsi_dh for
dm-multipath.
Sorry about the mishap.
chandra
On Thu, 2008-05-15 at 15:46 +0100, James Bottomley wrote:
> On Wed, 2008-05-14 at 14:13 -0700, Randy Dunlap wrote:
> > On Wed, 14 May 2008 01:01:29 -0700 Andrew Morton wrote:
> >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc2/2.6.26-rc2-mm1/
> >
> > SCSI_DH has some problems when CONFIG_SCSI=n:
> >
> > drivers/built-in.o: In function `activate_path':
> > dm-mpath.c:(.text+0x18a292): undefined reference to `scsi_dh_activate'
> > drivers/built-in.o: In function `multipath_ctr':
> > dm-mpath.c:(.text+0x18a6f0): undefined reference to `scsi_dh_handler_exist'
> > make[1]: *** [.tmp_vmlinux1] Error 1
> >
> >
> > #
> > # SCSI device support
> > #
> > CONFIG_RAID_ATTRS=y
> > # CONFIG_SCSI is not set
> > # CONFIG_SCSI_DMA is not set
> > # CONFIG_SCSI_NETLINK is not set
> > CONFIG_SCSI_DH=y
> > CONFIG_SCSI_DH_RDAC=y
> > CONFIG_SCSI_DH_HP_SW=y
> > CONFIG_SCSI_DH_EMC=y
>
> This is one more of those annoying selects. The SCSI_DH Kconfig file is
> correctly dependent on SCSI:
>
> menuconfig SCSI_DH
> tristate "SCSI Device Handlers"
> depends on SCSI
> default n
> help
>
> but we've also got a select in md/Kconfig:
>
> config DM_MULTIPATH
> tristate "Multipath target"
> depends on BLK_DEV_DM
> select SCSI_DH
>
> Which ignores the dependency.
>
> My best guess for fixing this is either to make the select a depends or
> just drop it altogether (after all, it's possible to have multipath on
> non-SCSI devices).
>
> James
>
>
[-- Attachment #2: remove_select_on_multipath --]
[-- Type: text/plain, Size: 1658 bytes --]
Do not automatically "select" SCSI_DH for dm-multipath. If SCSI_DH
doesn't exist,just do not allow hardware handlers to be used.
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
---
Index: scsi-misc-2.6/drivers/md/Kconfig
===================================================================
--- scsi-misc-2.6.orig/drivers/md/Kconfig
+++ scsi-misc-2.6/drivers/md/Kconfig
@@ -252,7 +252,6 @@ config DM_ZERO
config DM_MULTIPATH
tristate "Multipath target"
depends on BLK_DEV_DM
- select SCSI_DH
---help---
Allow volume managers to support multipath hardware.
Index: scsi-misc-2.6/drivers/md/dm-mpath.c
===================================================================
--- scsi-misc-2.6.orig/drivers/md/dm-mpath.c
+++ scsi-misc-2.6/drivers/md/dm-mpath.c
@@ -664,6 +664,8 @@ static int parse_hw_handler(struct arg_s
request_module("scsi_dh_%s", m->hw_handler_name);
if (scsi_dh_handler_exist(m->hw_handler_name) == 0) {
ti->error = "unknown hardware handler type";
+ kfree(m->hw_handler_name);
+ m->hw_handler_name = NULL;
return -EINVAL;
}
consume(as, hw_argc - 1);
Index: scsi-misc-2.6/include/scsi/scsi_dh.h
===================================================================
--- scsi-misc-2.6.orig/include/scsi/scsi_dh.h
+++ scsi-misc-2.6/include/scsi/scsi_dh.h
@@ -54,6 +54,16 @@ enum {
SCSI_DH_NOSYS,
SCSI_DH_DRIVER_MAX,
};
-
+#ifdef CONFIG_SCSI_DH
extern int scsi_dh_activate(struct request_queue *);
extern int scsi_dh_handler_exist(const char *);
+#else
+inline int scsi_dh_activate(struct request_queue *req)
+{
+ return 0;
+}
+inline int scsi_dh_handler_exist(const char *name)
+{
+ return 0;
+}
+#endif
next prev parent reply other threads:[~2008-05-15 19:57 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 8:01 2.6.26-rc2-mm1 Andrew Morton
2008-05-14 11:24 ` [BUG] 2.6.26-rc2-mm1 - kernel bug while bootup at __alloc_pages_internal () on x86_64 Kamalesh Babulal
2008-05-14 17:36 ` Andrew Morton
2008-05-14 18:21 ` Kamalesh Babulal
2008-05-14 19:44 ` Andrew Morton
2008-05-15 1:54 ` KAMEZAWA Hiroyuki
2008-05-18 8:00 ` Kamalesh Babulal
2008-05-18 17:07 ` KOSAKI Motohiro
2008-05-19 14:49 ` Lee Schermerhorn
2008-05-14 14:03 ` [BUG] 2.6.26-rc2-mm1 - kernel BUG at fs/reiserfs/journal.c:1414! Kamalesh Babulal
2008-05-14 18:01 ` Andrew Morton
2008-05-14 15:34 ` [BUG] 2.6.26-rc2-mm1 - kernel panic at inet_create() on powerpc Kamalesh Babulal
2008-05-14 16:07 ` Paul E. McKenney
2008-05-14 20:05 ` Alexey Dobriyan
2008-05-14 20:32 ` Paul E. McKenney
2008-05-14 18:29 ` 2.6.26-rc2-mm1: sparc64 - possible recursive locking detected Mariusz Kozlowski
2008-05-14 18:41 ` Andrew Morton
2008-05-14 18:50 ` Mariusz Kozlowski
2008-05-14 19:12 ` 2.6.26-rc2-mm1 Torsten Kaiser
2008-05-14 19:35 ` 2.6.26-rc2-mm1 Andrew Morton
2008-05-15 17:44 ` 2.6.26-rc2-mm1 Torsten Kaiser
2008-05-15 18:49 ` 2.6.26-rc2-mm1 Andrew Morton
2008-05-14 20:39 ` 2.6.26-rc2-mm1 (WARN() build error) Randy Dunlap
2008-05-14 20:43 ` 2.6.26-rc2-mm1 (CONFIG_*FD build errors) Randy Dunlap
2008-05-14 20:49 ` 2.6.26-rc2-mm1 Zan Lynx
2008-05-14 21:00 ` 2.6.26-rc2-mm1 Andrew Morton
2008-05-14 21:14 ` 2.6.26-rc2-mm1 me
2008-05-14 22:06 ` 2.6.26-rc2-mm1 Zan Lynx
2008-05-14 21:13 ` 2.6.26-rc2-mm1 (SCSI_DH build errors) Randy Dunlap
2008-05-15 14:46 ` James Bottomley
2008-05-15 19:56 ` Chandra Seetharaman [this message]
2008-05-23 3:25 ` Andrew Morton
2008-05-23 19:39 ` Chandra Seetharaman
2008-05-23 20:28 ` Randy Dunlap
2008-05-24 1:16 ` Chandra Seetharaman
2008-05-14 21:16 ` 2.6.26-rc2-mm1: sloooow mkfs.ext2 Alexey Dobriyan
2008-05-14 21:33 ` Alexey Dobriyan
2008-05-15 21:41 ` Jiri Slaby
2008-05-14 21:16 ` 2.6.26-rc2-mm1 (p9 build error when 9P_FS=n) Randy Dunlap
2008-05-15 0:00 ` Eric Van Hensbergen
2008-05-15 0:05 ` Andrew Morton
2008-05-15 2:29 ` Eric Van Hensbergen
2008-05-15 3:04 ` Andrew Morton
2008-05-15 3:53 ` Eric Van Hensbergen
2008-05-14 21:54 ` 2.6.26-rc2-mm1 Rafael J. Wysocki
2008-05-15 17:58 ` [PATCH] Re: 2.6.26-rc2-mm1 - fix parenthesis in include/asm-arm/arch-omap/control.h Mariusz Kozlowski
2008-05-15 17:59 ` [PATCH] Re: 2.6.26-rc2-mm1 - fix parenthesis in include/asm-mips/gic.h Mariusz Kozlowski
2008-05-15 18:01 ` [PATCH] Re: 2.6.26-rc2-mm1 - fix parenthesis in include/asm-mips/mach-au1x00/au1000.h Mariusz Kozlowski
2008-05-15 18:21 ` [BUG] Re: 2.6.26-rc2-mm1 - x86_32 oops on modprobe wusbcore Mariusz Kozlowski
2008-05-15 18:58 ` Andrew Morton
2008-05-15 20:05 ` Inaky Perez-Gonzalez
2008-05-16 22:17 ` 2.6.26-rc2-mm1: high speed something Alexey Dobriyan
2008-05-16 21:31 ` Andrew Morton
2008-05-16 22:00 ` Greg KH
2008-05-17 10:28 ` 2.6.26-rc2-mm1 and Linus -git: LEDS_TRIGGER_DEFAULT_ON odd default Valdis.Kletnieks
2008-05-19 11:33 ` 2.6.26-rc2-mm1 - machine stuck while booting up with CONFIG_FTRACE_STARTUP_TEST enabled Kamalesh Babulal
2008-05-19 13:02 ` Steven Rostedt
2008-05-19 14:08 ` Kamalesh Babulal
2008-05-19 14:38 ` Steven Rostedt
2008-05-20 10:01 ` 2.6.26-rc2-mm1: possible circular locking dependency detected Mariusz Kozlowski
2008-05-20 10:22 ` Andrew Morton
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=1210881374.21974.285.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox