patch sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch added to gregkh-2.6 tree

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <dan.j.williams@...>, <James.Bottomley@...>, <akpm@...>, <axboe@...>, <gregkh@...>, <hpa@...>, <htejun@...>, <jgarzik@...>, <kay.sievers@...>, <linux-ide@...>, <linux-kernel@...>, <linux-scsi@...>, <lkml@...>, <neilb@...>, <steve@...>, <torvalds@...>
Date: Wednesday, April 16, 2008 - 4:55 pm

This is a note to let you know that I've just added the patch titled

     Subject: sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor

to my gregkh-2.6 tree.  Its filename is

     sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch

This tree can be found at 
    http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/


From dan.j.williams@intel.com  Wed Apr 16 13:49:38 2008
From: Dan Williams <dan.j.williams@intel.com>
Date: Tue, 15 Apr 2008 16:43:15 -0700
Subject: sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor
To: Andrew Morton <akpm@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>, Kay Sievers <kay.sievers@vrfy.org>, Tejun Heo <htejun@gmail.com>, Mark Lord <lkml@rtr.ca>, Greg KH <gregkh@suse.de>, Jens Axboe <axboe@kernel.dk>, Jeff Garzik <jgarzik@pobox.com>, Linus Torvalds <torvalds@linux-foundation.org>, Linux Kernel <linux-kernel@vger.kernel.org>, IDE/ATA development list <linux-ide@vger.kernel.org>, linux-scsi <linux-scsi@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Message-ID: <1208302995.21877.12.camel@dwillia2-linux.ch.intel.com>


From: Dan Williams <dan.j.williams@intel.com>

Why?:
There are occasions where userspace would like to access sysfs
attributes for a device but it may not know how sysfs has named the
device or the path.  For example what is the sysfs path for
/dev/disk/by-id/ata-ST3160827AS_5MT004CK?  With this change a call to
stat(2) returns the major:minor then userspace can see that
/sys/dev/block/8:32 links to /sys/block/sdc.

What are the alternatives?:
1/ Add an ioctl to return the path: Doable, but sysfs is meant to reduce
   the need to proliferate ioctl interfaces into the kernel, so this
   seems counter productive.

2/ Use udev to create these symlinks: Also doable, but it adds a
   udev dependency to utilities that might be running in a limited
   environment like an initramfs.

3/ Do a full-tree search of sysfs.

Cc: Neil Brown <neilb@suse.de>
Cc: Tejun Heo <htejun@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <gregkh@suse.de>
Acked-by: Mark Lord <lkml@rtr.ca>
Acked-by: H. Peter Anvin <hpa@zytor.com>
Reviewed-by: SL Baur <steve@xemacs.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

---
 Documentation/filesystems/sysfs.txt |    6 ++++
 drivers/base/core.c                 |   46 +++++++++++++++++++++++++++++++++++-
 2 files changed, 51 insertions(+), 1 deletion(-)

--- a/Documentation/filesystems/sysfs.txt
+++ b/Documentation/filesystems/sysfs.txt
@@ -248,6 +248,7 @@ The top level sysfs directory looks like
 block/
 bus/
 class/
+dev/
 devices/
 firmware/
 net/
@@ -274,6 +275,11 @@ fs/ contains a directory for some filesy
 filesystem wanting to export attributes must create its own hierarchy
 below fs/ (see ./fuse.txt for an example).
 
+dev/ contains two directories char/ and block/. Inside these two
+directories there are symlinks named <major>:<minor>.  These symlinks
+point to the sysfs directory for the given device.  /sys/dev provides a
+quick way to lookup the sysfs interface for a device from the result of
+a stat(2) operation.
 
 More information can driver-model specific features can be found in
 Documentation/driver-model/. 
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -27,6 +27,9 @@
 
 int (*platform_notify)(struct device *dev) = NULL;
 int (*platform_notify_remove)(struct device *dev) = NULL;
+static struct kobject *dev_kobj;
+static struct kobject *char_kobj;
+static struct kobject *block_kobj;
 
 #ifdef CONFIG_BLOCK
 static inline int device_is_not_partition(struct device *dev)
@@ -760,6 +763,11 @@ static void device_remove_class_symlinks
 	sysfs_remove_link(&dev->kobj, "subsystem");
 }
 
+static struct kobject *device_to_dev_kobj(struct device *dev)
+{
+	return dev->class == &block_class ? block_kobj : char_kobj;
+}
+
 /**
  * device_add - add device to device hierarchy.
  * @dev: device.
@@ -776,6 +784,7 @@ int device_add(struct device *dev)
 	struct device *parent = NULL;
 	struct class_interface *class_intf;
 	int error;
+	char devt_str[15];
 
 	dev = get_device(dev);
 	if (!dev || !strlen(dev->bus_id)) {
@@ -807,9 +816,16 @@ int device_add(struct device *dev)
 		goto attrError;
 
 	if (MAJOR(dev->devt)) {
+		struct kobject *kobj = device_to_dev_kobj(dev);
+
 		error = device_create_file(dev, &devt_attr);
 		if (error)
 			goto ueventattrError;
+
+		format_dev_t(devt_str, dev->devt);
+		error = sysfs_create_link(kobj, &dev->kobj, devt_str);
+		if (error)
+			goto devtattrError;
 	}
 
 	error = device_add_class_symlinks(dev);
@@ -854,6 +870,9 @@ int device_add(struct device *dev)
 	device_remove_class_symlinks(dev);
  SymlinkError:
 	if (MAJOR(dev->devt))
+		sysfs_remove_link(device_to_dev_kobj(dev), devt_str);
+ devtattrError:
+	if (MAJOR(dev->devt))
 		device_remove_file(dev, &devt_attr);
  ueventattrError:
 	device_remove_file(dev, &uevent_attr);
@@ -925,12 +944,16 @@ void device_del(struct device *dev)
 {
 	struct device *parent = dev->parent;
 	struct class_interface *class_intf;
+	char devt_str[15];
 
 	device_pm_remove(dev);
 	if (parent)
 		klist_del(&dev->knode_parent);
-	if (MAJOR(dev->devt))
+	if (MAJOR(dev->devt)) {
+		format_dev_t(devt_str, dev->devt);
+		sysfs_remove_link(device_to_dev_kobj(dev), devt_str);
 		device_remove_file(dev, &devt_attr);
+	}
 	if (dev->class) {
 		device_remove_class_symlinks(dev);
 
@@ -1055,7 +1078,25 @@ int __init devices_init(void)
 	devices_kset = kset_create_and_add("devices", &device_uevent_ops, NULL);
 	if (!devices_kset)
 		return -ENOMEM;
+	dev_kobj = kobject_create_and_add("dev", NULL);
+	if (!dev_kobj)
+		goto dev_kobj_err;
+	block_kobj = kobject_create_and_add("block", dev_kobj);
+	if (!block_kobj)
+		goto block_kobj_err;
+	char_kobj = kobject_create_and_add("char", dev_kobj);
+	if (!char_kobj)
+		goto char_kobj_err;
+
 	return 0;
+
+ char_kobj_err:
+	kobject_put(block_kobj);
+ block_kobj_err:
+	kobject_put(dev_kobj);
+ dev_kobj_err:
+	kset_unregister(devices_kset);
+	return -ENOMEM;
 }
 
 EXPORT_SYMBOL_GPL(device_for_each_child);
@@ -1351,4 +1392,7 @@ void device_shutdown(void)
 			dev->driver->shutdown(dev);
 		}
 	}
+	kobject_put(char_kobj);
+	kobject_put(block_kobj);
+	kobject_put(dev_kobj);
 }


Patches currently in gregkh-2.6 which might be from dan.j.williams@intel.com are

driver-core/sysfs-refill-attribute-buffer-when-reading-from-offset-0.patch
driver-core/sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Mar 25, 12:02 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, James Bottomley, (Tue Mar 25, 11:17 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Greg Freemyer, (Tue Mar 25, 1:45 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Matt Domsch, (Sun Mar 30, 12:28 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Randy Dunlap, (Tue Mar 25, 1:52 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Matthew Wilcox, (Tue Mar 25, 2:09 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Boaz Harrosh, (Wed Mar 26, 5:58 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Mar 25, 1:31 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, James Bottomley, (Tue Mar 25, 3:32 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Mar 25, 1:13 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Mar 25, 9:37 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Mar 25, 9:55 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Mar 25, 1:37 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Mar 25, 8:34 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Kay Sievers, (Thu Mar 27, 2:51 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Thu Mar 27, 2:55 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Kay Sievers, (Thu Mar 27, 3:03 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Tejun Heo, (Tue Mar 25, 8:54 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Kay Sievers, (Thu Mar 27, 3:29 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Thu Mar 27, 3:38 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Dan Williams, (Fri Apr 11, 7:25 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Andrew Morton, (Tue Apr 15, 3:18 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, James Bottomley, (Tue Apr 15, 10:20 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Apr 15, 2:16 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Dan Williams, (Tue Apr 15, 7:43 pm)
patch sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-m..., , (Wed Apr 16, 4:55 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Mark Lord, (Tue Apr 15, 9:47 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Tejun Heo, (Wed Mar 26, 12:24 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Wed Mar 26, 2:04 am)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Randy Dunlap, (Tue Mar 25, 3:34 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Mar 25, 4:36 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Mar 25, 5:26 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Matthew Wilcox, (Thu Mar 27, 3:05 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, H. Peter Anvin, (Tue Mar 25, 7:05 pm)
Re: What to do about the 2TB limit on HDIO_GETGEO ?, Andrew Morton, (Tue Mar 25, 12:19 am)