are the dm target ioctl handlers extensible to serving arbitrary configuration ioctls?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



And if so, how would I connect to them from userland? 

What would be the device that i opened for reading and writing?

Based on my review of the code, it seems that these particular ioctl servicing routines are designed to service DM or block device specific ioctls and not designed to support setting or getting configuration information about the particular dm target instance.

Specifically, i wish to be able to use an ioctl to set and get the number of zones and other things in the dm-zacsim.ko that i am currently coding.

Here is the ioctl handler implementation in dm-linear.c that is an example of the ioctl handler that i am asking about:


static int linear_ioctl(struct dm_target *ti, unsigned int cmd,
117                         unsigned long arg)
118 {
119         struct linear_c *lc = (struct linear_c *) ti->private;
120         struct dm_dev *dev = lc->dev;
121         int r = 0;

              // CAN I ADD MY OWN ARBITRARY STUFF IN HERE?

122 
123         /*
124          * Only pass ioctls through if the device sizes match exactly.
125          */
126         if (lc->start ||
127             ti->len != i_size_read(dev->bdev->bd_inode) >> SECTOR_SHIFT)
128                 r = scsi_verify_blk_ioctl(NULL, cmd);
129 
130         return r ? : __blkdev_driver_ioctl(dev->bdev, dev->mode, cmd, arg);
131 }

tnx!

johnu

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux