James Bottomley wrote:
> On Sun, 2009-01-25 at 16:58 +0200, Boaz Harrosh wrote:
>> Kernel clients like exofs can retrieve struct osd_dev(s)
>> by means of below API.
>>
>> + osduld_path_lookup() - given a path (e.g "/dev/osd0") locks and
>> returns the corresponding struct osd_dev, which is then needed
>> for subsequent libosd use.
>>
>> + osduld_put_device() - free up use of an osd_dev.
>>
>> Devices can be shared by multiple clients. The osd_uld_device's
>> life time is governed by an embedded kref structure.
>>
>> The osd_uld_device holds an extra reference to both it's
>> char-device and it's scsi_device, and will release these just
>> before the final deallocation.
>>
>> There are three possible lock sources of the osd_uld_device
>> 1. First and for most is the probe() function called by
>> scsi-ml upon a successful login into a target. Released in release()
>> when logout.
>> 2. Second by user-mode file handles opened on the char-dev.
>> 3. Third is here by Kernel users.
>> All three locks must be removed before the osd_uld_device is freed.
>>
>> The MODULE has three lock sources as well:
>> 1. scsi-ml at probe() time, removed after release(). (login/logout)
>> 2. The user-mode file handles open/close.
>> 3. Import symbols by client modules like exofs.
>>
>> TODO:
>> This API is not enough for the pNFS-objects LD. A more versatile
>> API will be needed. Proposed API could be:
>> struct osd_dev *osduld_sysid_lookup(const char id[OSD_SYSTEMID_LEN]);
>>
>> Signed-off-by: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
>> ---
>> drivers/scsi/osd/osd_uld.c | 63 ++++++++++++++++++++++++++++++++++++++++++
>> include/scsi/osd_initiator.h | 4 ++
>> 2 files changed, 67 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/scsi/osd/osd_uld.c b/drivers/scsi/osd/osd_uld.c
>> index f6f9a99..cd4ca7c 100644
>> --- a/drivers/scsi/osd/osd_uld.c
>> +++ b/drivers/scsi/osd/osd_uld.c
>> @@ -173,6 +173,69 @@ static const struct file_operations osd_fops = {
>> .unlocked_ioctl = osd_uld_ioctl,
>> };
>>
>> +struct osd_dev *osduld_path_lookup(const char *path)
>
> Is there no other way to do this? A kernel component opening another
> kernel component by device path is generally frowned upon.
>
> The way it should work is to have a user space process initiate
> everything because it can see the full device space and cope with the
> problems that may occur on first open in user space.
>
Thank you for asking, this is something I was pondering on for a long
time.
I have based this work on the block-devices model and the way filesystems
mount a block device. In fact I have started with lookup_bdev() as reference
and only changed it slightly to match char-devices. I have looked in other
parts of the kernel on what do the few "FSs over char-dev" do, (there are a few)
and they all invent their own none-standard way of mount-options to denote a device
to load. While the actual mount-path is unused/empty. I thought it is much more
natural to the user of the mount command to just give the device path, just as if
it is a block-device. The way I see it, which was triggered by a lot of what you said,
an OSD device is just an advanced-API storage-device and all the rest of the stuff
should be as natural as possible.
That said, I'm very open to suggestions. What would be a better/more standard way
for an OSD based filesystem to look up it's devices, that could be easily denoted
by the mount command?
[Please note that with above solution, contrary to all other solutions I've seen
except block-dev of course, I do not keep any list of OSD devices anywhere. The
vfs /dev/ directory does that for us. This, I would say, is a nice advantage no
duplicate lists]
However I have a question. I'm CCing fsdevel maybe someone there could help.
Please see below, at the exact code that fails.
>> +{
>> + struct nameidata nd;
>> + struct inode *inode;
>> + struct cdev *cdev;
>> + struct osd_uld_device *uninitialized_var(oud);
>> + int error;
>> +
>> + if (!path || !*path) {
>> + OSD_ERR("Mount with !path || !*path\n");
>> + return ERR_PTR(-EINVAL);
>> + }
>> +
>> + error = path_lookup(path, LOOKUP_FOLLOW, &nd);
>> + if (error) {
>> + OSD_ERR("path_lookup of %s faild=>%d\n", path, error);
>> + return ERR_PTR(error);
>> + }
>> +
>> + inode = nd.path.dentry->d_inode;
>> + error = -EINVAL; /* Not the right device e.g osd_uld_device */
>> + if (!S_ISCHR(inode->i_mode)) {
>> + OSD_DEBUG("!S_ISCHR()\n");
>> + goto out;
>> + }
>> +
>> + cdev = inode->i_cdev;
>> + if (!cdev) {
>> + OSD_ERR("Before mounting an OSD Based filesystem\n");
>> + OSD_ERR(" user-mode must open+close the %s device\n", path);
>> + OSD_ERR(" Example: bash: echo < %s\n", path);
>> + goto out;
>> + }
Here at this point, as it says by the error message, if I do not open the
device at least once in the life time of the char-device the check fails.
The device-inode is only half baked. My mount script just does a fast open+close
before it mounts exofs. Couple of questions:
* Is there something I can trigger from Kernel prior to the path_lookup() call
that will force the inode binding to the char-device. Just like user-mode open
does.
* How is lookup_bdev() different then what I do, in that it does not have that open/close
problem?
>> +
>> + /* The Magic wand. Is it our char-dev */
>> + /* TODO: Support sg devices */
>> + if (cdev->owner != THIS_MODULE) {
>> + OSD_ERR("Error mounting %s - is not an OSD device\n", path);
>> + goto out;
>> + }
>> +
>> + oud = container_of(cdev, struct osd_uld_device, cdev);
>> +
>> + __uld_get(oud);
>> + error = 0;
>> +
>> +out:
>> + path_put(&nd.path);
>> + return error ? ERR_PTR(error) : &oud->od;
>> +}
>> +EXPORT_SYMBOL(osduld_path_lookup);
>> +
>> +void osduld_put_device(struct osd_dev *od)
>> +{
>> + if (od) {
>> + struct osd_uld_device *oud = container_of(od,
>> + struct osd_uld_device, od);
>> +
>> + __uld_put(oud);
>> + }
>> +}
>> +EXPORT_SYMBOL(osduld_put_device);
>> +
>> /*
>> * Scsi Device operations
>> */
>> diff --git a/include/scsi/osd_initiator.h b/include/scsi/osd_initiator.h
>> index a5dbbdd..e84dc7a 100644
>> --- a/include/scsi/osd_initiator.h
>> +++ b/include/scsi/osd_initiator.h
>> @@ -33,6 +33,10 @@ struct osd_dev {
>> unsigned def_timeout;
>> };
>>
>> +/* Retrieve/return osd_dev(s) for use by Kernel clients */
>> +struct osd_dev *osduld_path_lookup(const char *dev_name); /*Use IS_ERR/ERR_PTR*/
>> +void osduld_put_device(struct osd_dev *od);
>> +
>> /* Add/remove test ioctls from external modules */
>> typedef int (do_test_fn)(struct osd_dev *od, unsigned cmd, unsigned long arg);
>> int osduld_register_test(unsigned ioctl, do_test_fn *do_test);
>> --
Thanks for reviewing
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
