From: Stephen Cameron <steve.cameron@hp.com>
To: linux-kernel@vger.kernel.org
Cc: axboe@suse.de
Subject: [PATCH] 2.5.43 cciss rescan disk ioctl
Date: Fri, 18 Oct 2002 09:49:10 -0600 [thread overview]
Message-ID: <20021018094910.A856@zuul.cca.cpqcorp.net> (raw)
Adds CCISS_RESCANDISK ioctl. Applies to 2.5.43 after the
previous 9 patches I sent.
-- steve
This is meant to be used in a configuration like
Steeleye's Lifekeeper. Two hosts connect to the storage, one
reserves disks. The 2nd will not be able to read the partition
information because of the reservations. In the event the 1st
system fails, the 2nd can detect this, (via special hardware +
software typically) and then take over the storage and rescan
the disks via this ioctl.
diff -urN linux-2.5.43-i/drivers/block/cciss.c linux-2.5.43-j/drivers/block/cciss.c
--- linux-2.5.43-i/drivers/block/cciss.c Thu Oct 17 13:20:30 2002
+++ linux-2.5.43-j/drivers/block/cciss.c Thu Oct 17 13:28:23 2002
@@ -46,12 +46,12 @@
#include <linux/completion.h>
#define CCISS_DRIVER_VERSION(maj,min,submin) ((maj<<16)|(min<<8)|(submin))
-#define DRIVER_NAME "Compaq CISS Driver (v 2.5.0)"
-#define DRIVER_VERSION CCISS_DRIVER_VERSION(2,5,0)
+#define DRIVER_NAME "Compaq CISS Driver (v 2.5.1)"
+#define DRIVER_VERSION CCISS_DRIVER_VERSION(2,5,1)
/* Embedded module documentation macros - see modules.h */
MODULE_AUTHOR("Charles M. White III - Compaq Computer Corporation");
-MODULE_DESCRIPTION("Driver for Compaq Smart Array Controller 5xxx v. 2.5.0");
+MODULE_DESCRIPTION("Driver for Compaq Smart Array Controller 5xxx v. 2.5.1");
MODULE_LICENSE("GPL");
#include "cciss_cmd.h"
@@ -108,6 +108,7 @@
static int cciss_revalidate(kdev_t dev);
static int deregister_disk(int ctlr, int logvol);
static int register_new_disk(int cltr);
+static int cciss_rescan_disk(int cltr, int logvol);
static void cciss_getgeometry(int cntl_num);
@@ -351,13 +352,22 @@
return -ENXIO;
/*
* Root is allowed to open raw volume zero even if its not configured
- * so array config can still work. I don't think I really like this,
+ * so array config can still work. Root is also allowed to open any
+ * volume that has a LUN ID, so it can issue IOCTL to reread the
+ * disk information. I don't think I really like this,
* but I'm already using way to many device nodes to claim another one
* for "raw controller".
*/
if (hba[ctlr]->drv[dsk].nr_blocks == 0) {
- if (minor(inode->i_rdev) != 0)
- return -ENXIO;
+ if (minor(inode->i_rdev) != 0) {
+ /* if not node 0 make sure it is a partition = 0 */
+ if (minor(inode->i_rdev) & 0x0f)
+ return -ENXIO;
+ /* if it is, make sure we have a LUN ID */
+ if (hba[ctlr]->drv[minor(inode->i_rdev)
+ >> NWD_SHIFT].LunID == 0)
+ return -ENXIO;
+ }
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
}
@@ -574,6 +584,9 @@
case CCISS_REVALIDVOLS:
return( revalidate_allvol(inode->i_rdev));
+ case CCISS_RESCANDISK:
+ return(cciss_rescan_disk(ctlr, dsk));
+
case CCISS_GETLUNINFO: {
LogvolInfo_struct luninfo;
struct gendisk *disk = hba[ctlr]->gendisk[dsk];
@@ -1253,6 +1266,52 @@
kfree(size_buff);
kfree(inq_buff);
return (logvol);
+}
+static int cciss_rescan_disk(int ctlr, int logvol)
+{
+ /* this is meant to be used in a configuration like
+ Steeleye's Lifekeeper. Two hosts connect to the storage, one
+ reserves disks. The 2nd will not be able to read the partition
+ information because of the reservations. In the event the 1st
+ system fails, the 2nd can detect this, (via special hardware +
+ software typically) and then take over the storage and rescan
+ the disks via this ioctl. */
+
+ struct gendisk *disk = hba[ctlr]->gendisk[logvol];
+ ReadCapdata_struct *size_buff;
+ InquiryData_struct *inq_buff;
+ unsigned int block_size;
+ unsigned int total_size;
+ kdev_t kdev;
+ struct block_device *bdev;
+
+ if (!capable(CAP_SYS_RAWIO))
+ return -EPERM;
+ if (hba[ctlr]->drv[logvol].nr_blocks != 0) {
+ /* disk is possibly on line, return just a warning */
+ return 1;
+ }
+ size_buff = kmalloc(sizeof( ReadCapdata_struct), GFP_KERNEL);
+ if (size_buff == NULL) {
+ printk(KERN_ERR "cciss: out of memory\n");
+ return -1;
+ }
+ inq_buff = kmalloc(sizeof( InquiryData_struct), GFP_KERNEL);
+ if (inq_buff == NULL) {
+ printk(KERN_ERR "cciss: out of memory\n");
+ kfree(size_buff);
+ return -1;
+ }
+ cciss_read_capacity(ctlr, logvol, size_buff, 1, &total_size,
+ &block_size);
+ cciss_geometry_inquiry(ctlr, logvol, 1, total_size, block_size,
+ inq_buff, &hba[ctlr]->drv[logvol]);
+ kdev = mk_kdev(MAJOR_NR + ctlr, disk->first_minor);
+ bdev = bdget(kdev_t_to_nr(kdev));
+ rescan_partitions(disk, bdev);
+ kfree(size_buff);
+ kfree(inq_buff);
+ return(0);
}
/*
* Wait polling for a command to complete.
diff -urN linux-2.5.43-i/include/linux/cciss_ioctl.h linux-2.5.43-j/include/linux/cciss_ioctl.h
--- linux-2.5.43-i/include/linux/cciss_ioctl.h Thu Oct 17 13:21:16 2002
+++ linux-2.5.43-j/include/linux/cciss_ioctl.h Thu Oct 17 13:29:05 2002
@@ -195,6 +195,7 @@
#define CCISS_REGNEWDISK _IOW(CCISS_IOC_MAGIC, 13, int)
#define CCISS_REGNEWD _IO(CCISS_IOC_MAGIC, 14)
+#define CCISS_RESCANDISK _IO(CCISS_IOC_MAGIC, 16)
#define CCISS_GETLUNINFO _IOR(CCISS_IOC_MAGIC, 17, LogvolInfo_struct)
#endif
next reply other threads:[~2002-10-18 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 15:49 Stephen Cameron [this message]
2002-10-18 16:05 ` Alexander Viro
2002-10-18 16:43 Cameron, Steve
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=20021018094910.A856@zuul.cca.cpqcorp.net \
--to=steve.cameron@hp.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®