---
 block/genhd.c            |    5 -
 drivers/base/bus.c       |   22 ------
 drivers/base/class.c     |   25 -------
 drivers/base/core.c      |  164 -----------------------------------------------
 drivers/scsi/hosts.c     |    2 
 drivers/scsi/scsi_scan.c |    2 
 fs/partitions/check.c    |    6 -
 include/sound/core.h     |    6 -
 init/Kconfig             |   36 ----------
 sound/core/init.c        |   11 ---
 10 files changed, 7 insertions(+), 272 deletions(-)

block/genhd.c +1 -4

@@ -22,9 +22,7 @@
 #include "blk.h"
 
 static DEFINE_MUTEX(block_class_lock);
-#ifndef CONFIG_SYSFS_DEPRECATED
 struct kobject *block_depr;
-#endif
 
 /* for extended dynamic devt allocation, currently only one major is used */
 #define MAX_EXT_DEVT		(1 << MINORBITS)

@@ -803,10 +801,9 @@ static int __init genhd_device_init(void
 
 	register_blkdev(BLOCK_EXT_MAJOR, "blkext");
 
-#ifndef CONFIG_SYSFS_DEPRECATED
 	/* create top-level block dir */
 	block_depr = kobject_create_and_add("block", NULL);
-#endif
+
 	return 0;
 }

drivers/base/bus.c +0 ~~-22~~

@@ -440,22 +440,6 @@ static void device_remove_attrs(struct b
 	}
 }
 
-#ifdef CONFIG_SYSFS_DEPRECATED
-static int make_deprecated_bus_links(struct device *dev)
-{
-	return sysfs_create_link(&dev->kobj,
-				 &dev->bus->p->subsys.kobj, "bus");
-}
-
-static void remove_deprecated_bus_links(struct device *dev)
-{
-	sysfs_remove_link(&dev->kobj, "bus");
-}
-#else
-static inline int make_deprecated_bus_links(struct device *dev) { return 0; }
-static inline void remove_deprecated_bus_links(struct device *dev) { }
-#endif
-
 /**
  * bus_add_device - add device to bus
  * @dev: device being added

@@ -482,15 +466,10 @@ int bus_add_device(struct device *dev)
 				&dev->bus->p->subsys.kobj, "subsystem");
 		if (error)
 			goto out_subsys;
-		error = make_deprecated_bus_links(dev);
-		if (error)
-			goto out_deprecated;
 		klist_add_tail(&dev->p->knode_bus, &bus->p->klist_devices);
 	}
 	return 0;
 
-out_deprecated:
-	sysfs_remove_link(&dev->kobj, "subsystem");
 out_subsys:
 	sysfs_remove_link(&bus->p->devices_kset->kobj, dev_name(dev));
 out_id:

@@ -530,7 +509,6 @@ void bus_remove_device(struct device *de
 {
 	if (dev->bus) {
 		sysfs_remove_link(&dev->kobj, "subsystem");
-		remove_deprecated_bus_links(dev);
 		sysfs_remove_link(&dev->bus->p->devices_kset->kobj,
 				  dev_name(dev));
 		device_remove_attrs(dev->bus, dev);

drivers/base/class.c +0 ~~-25~~

@@ -184,13 +184,7 @@ int __class_register(struct class *cls,
 	if (!cls->dev_kobj)
 		cls->dev_kobj = sysfs_dev_char_kobj;
 
-#if defined(CONFIG_SYSFS_DEPRECATED) && defined(CONFIG_BLOCK)
-	/* let the block class directory show up in the root of sysfs */
-	if (cls != &block_class)
-		cp->class_subsys.kobj.kset = class_kset;
-#else
 	cp->class_subsys.kobj.kset = class_kset;
-#endif
 	cp->class_subsys.kobj.ktype = &class_ktype;
 	cp->class = cls;
 	cls->p = cp;

@@ -276,25 +270,6 @@ void class_destroy(struct class *cls)
 	class_unregister(cls);
 }
 
-#ifdef CONFIG_SYSFS_DEPRECATED
-char *make_class_name(const char *name, struct kobject *kobj)
-{
-	char *class_name;
-	int size;
-
-	size = strlen(name) + strlen(kobject_name(kobj)) + 2;
-
-	class_name = kmalloc(size, GFP_KERNEL);
-	if (!class_name)
-		return NULL;
-
-	strcpy(class_name, name);
-	strcat(class_name, ":");
-	strcat(class_name, kobject_name(kobj));
-	return class_name;
-}
-#endif
-
 /**
  * class_dev_iter_init - initialize class device iterator
  * @iter: class iterator to initialize

drivers/base/core.c +1 ~~-163~~

239 lines not on this page · raw message

drivers/scsi/hosts.c +0 -2

@@ -406,9 +406,7 @@ struct Scsi_Host *scsi_host_alloc(struct
 
 	device_initialize(&shost->shost_gendev);
 	dev_set_name(&shost->shost_gendev, "host%d", shost->host_no);
-#ifndef CONFIG_SYSFS_DEPRECATED
 	shost->shost_gendev.bus = &scsi_bus_type;
-#endif
 	shost->shost_gendev.type = &scsi_host_type;
 
 	device_initialize(&shost->shost_dev);

drivers/scsi/scsi_scan.c +0 -2

@@ -417,9 +417,7 @@ static struct scsi_target *scsi_alloc_ta
 	starget->reap_ref = 1;
 	dev->parent = get_device(parent);
 	dev_set_name(dev, "target%d:%d:%d", shost->host_no, channel, id);
-#ifndef CONFIG_SYSFS_DEPRECATED
 	dev->bus = &scsi_bus_type;
-#endif
 	dev->type = &scsi_target_type;
 	starget->id = id;
 	starget->channel = channel;

fs/partitions/check.c +2 -4

@@ -500,14 +500,14 @@ void register_disk(struct gendisk *disk)
 
 	if (device_add(ddev))
 		return;
-#ifndef CONFIG_SYSFS_DEPRECATED
+
 	err = sysfs_create_link(block_depr, &ddev->kobj,
 				kobject_name(&ddev->kobj));
 	if (err) {
 		device_del(ddev);
 		return;
 	}
-#endif
+
 	disk->part0.holder_dir = kobject_create_and_add("holders", &ddev->kobj);
 	disk->slave_dir = kobject_create_and_add("slaves", &ddev->kobj);

@@ -724,8 +724,6 @@ void del_gendisk(struct gendisk *disk)
 	kobject_put(disk->part0.holder_dir);
 	kobject_put(disk->slave_dir);
 	disk->driverfs_dev = NULL;
-#ifndef CONFIG_SYSFS_DEPRECATED
 	sysfs_remove_link(block_depr, dev_name(disk_to_dev(disk)));
-#endif
 	device_del(disk_to_dev(disk));
 }

include/sound/core.h +0 -6

@@ -133,9 +133,7 @@ struct snd_card {
 	int free_on_last_close;		/* free in context of file_release */
 	wait_queue_head_t shutdown_sleep;
 	struct device *dev;		/* device assigned to this card */
-#ifndef CONFIG_SYSFS_DEPRECATED
 	struct device *card_dev;	/* cardX object for sysfs */
-#endif
 
 #ifdef CONFIG_PM
 	unsigned int power_state;	/* power state */

@@ -196,11 +194,7 @@ struct snd_minor {
 /* return a device pointer linked to each sound device as a parent */
 static inline struct device *snd_card_get_device_link(struct snd_card *card)
 {
-#ifdef CONFIG_SYSFS_DEPRECATED
-	return card ? card->dev : NULL;
-#else
 	return card ? card->card_dev : NULL;
-#endif
 }
 
 /* sound.c */

init/Kconfig +0 ~~-36~~

@@ -651,42 +651,6 @@ endif # CGROUPS
 config MM_OWNER
 	bool
 
-config SYSFS_DEPRECATED
-	bool
-
-config SYSFS_DEPRECATED_V2
-	bool "enable deprecated sysfs features to support old userspace tools"
-	depends on SYSFS
-	default n
-	select SYSFS_DEPRECATED
-	help
-	  This option switches the layout of sysfs to the deprecated
-	  version. Do not use it on recent distributions.
-
-	  The current sysfs layout features a unified device tree at
-	  /sys/devices/, which is able to express a hierarchy between
-	  class devices. If the deprecated option is set to Y, the
-	  unified device tree is split into a bus device tree at
-	  /sys/devices/ and several individual class device trees at
-	  /sys/class/. The class and bus devices will be connected by
-	  "<subsystem>:<name>" and the "device" links. The "block"
-	  class devices, will not show up in /sys/class/block/. Some
-	  subsystems will suppress the creation of some devices which
-	  depend on the unified device tree.
-
-	  This option is not a pure compatibility option that can
-	  be safely enabled on newer distributions. It will change the
-	  layout of sysfs to the non-extensible deprecated version,
-	  and disable some features, which can not be exported without
-	  confusing older userspace tools. Since 2007/2008 all major
-	  distributions do not enable this option, and ship no tools which
-	  depend on the deprecated layout or this option.
-
-	  If you are using a new kernel on an older distribution, or use
-	  older userspace tools, you might need to say Y here. Do not say Y,
-	  if the original kernel, that came with your distribution, has
-	  this option set to N.
-
 config RELAY
 	bool "Kernel->user space relay support (formerly relayfs)"
 	help

sound/core/init.c +3 -8

@@ -395,12 +395,10 @@ int snd_card_disconnect(struct snd_card
 		snd_printk(KERN_ERR "not all devices for card %i can be disconnected\n", card->number);
 
 	snd_info_card_disconnect(card);
-#ifndef CONFIG_SYSFS_DEPRECATED
 	if (card->card_dev) {
 		device_unregister(card->card_dev);
 		card->card_dev = NULL;
 	}
-#endif
 #ifdef CONFIG_PM
 	wake_up(&card->power_sleep);
 #endif

@@ -573,7 +571,6 @@ void snd_card_set_id(struct snd_card *ca
 }
 EXPORT_SYMBOL(snd_card_set_id);
 
-#ifndef CONFIG_SYSFS_DEPRECATED
 static ssize_t
 card_id_show_attr(struct device *dev,
 		  struct device_attribute *attr, char *buf)

@@ -630,7 +627,6 @@ card_number_show_attr(struct device *dev
 
 static struct device_attribute card_number_attrs =
 	__ATTR(number, S_IRUGO, card_number_show_attr, NULL);
-#endif /* CONFIG_SYSFS_DEPRECATED */
 
 /**
  *  snd_card_register - register the soundcard

@@ -649,7 +645,7 @@ int snd_card_register(struct snd_card *c
 
 	if (snd_BUG_ON(!card))
 		return -EINVAL;
-#ifndef CONFIG_SYSFS_DEPRECATED
+
 	if (!card->card_dev) {
 		card->card_dev = device_create(sound_class, card->dev,
 					       MKDEV(0, 0), card,

@@ -657,7 +653,7 @@ int snd_card_register(struct snd_card *c
 		if (IS_ERR(card->card_dev))
 			card->card_dev = NULL;
 	}
-#endif
+
 	if ((err = snd_device_register_all(card)) < 0)
 		return err;
 	mutex_lock(&snd_card_mutex);

@@ -674,7 +670,6 @@ int snd_card_register(struct snd_card *c
 	if (snd_mixer_oss_notify_callback)
 		snd_mixer_oss_notify_callback(card, SND_MIXER_OSS_NOTIFY_REGISTER);
 #endif
-#ifndef CONFIG_SYSFS_DEPRECATED
 	if (card->card_dev) {
 		err = device_create_file(card->card_dev, &card_id_attrs);
 		if (err < 0)

@@ -683,7 +678,7 @@ int snd_card_register(struct snd_card *c
 		if (err < 0)
 			return err;
 	}
-#endif
+
 	return 0;
 }

Andrew Morton

2010-07-14 23:38 UTC #1 lore raw

Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:

This is no longer needed by any userspace tools, so it's safe to remove.

Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:

@@ -106,8 +106,7 @@
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set

and the box still won't boot.

Dave Airlie

2010-07-15 00:24 UTC #2 lore raw

Quoted 5 lines · Andrew Morton

Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.

Also still used for booting mainline kernels on RHEL5 userspaces.

Live with your mistakes guys, don't try and bury them.

Dave.

Greg KH

author

2010-07-15 04:14 UTC #3 lore raw

Quoted 9 lines · Dave Airlie

Quoted 5 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Also still used for booting mainline kernels on RHEL5 userspaces.

Really? I thought that was fixed a long time ago. What kernel was RHEL5 originally based on?

And note that no RHEL5 user is going to be using a .36 kernel on their system, that's a completely unsupported and unadvised situation. Heck, I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?

Quoted 1 line

Live with your mistakes guys, don't try and bury them.

I'm not, I honestly thought that we had resolved these issues.

So, which version of Centos matches up with RHEL5 so I can go download it and see if I can resolve this? We might just be able to reduce the ammount of code we remove here and keep the Kconfig option around, if that old userspace is expecting a portion of the symlinks to still be present.

thanks,

greg k-h

Dave Airlie

2010-07-15 05:00 UTC #4 lore raw

Quoted 9 lines · Greg KH

Quoted 8 lines · Dave Airlie
Quoted 5 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.

Quoted 9 lines

Quoted 1 line
Also still used for booting mainline kernels on RHEL5 userspaces.
Really? I thought that was fixed a long time ago. What kernel was RHEL5 originally based on?
And note that no RHEL5 user is going to be using a .36 kernel on their system, that's a completely unsupported and unadvised situation. Heck, I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?

I think some people do it internally, last time I did it was to test something I was backporting, so you want to make sure the upstream version boots and the backported version also boots on the same hw/userspace.

original kernel was 2.6.18.

Dave.

Greg KH

author

2010-07-15 05:35 UTC #5 lore raw

Quoted 20 lines · Dave Airlie

Quoted 9 lines · Greg KH
Quoted 8 lines · Dave Airlie
Quoted 5 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Quoted 9 lines
Quoted 1 line
Also still used for booting mainline kernels on RHEL5 userspaces.
Really? ?I thought that was fixed a long time ago. ?What kernel was RHEL5 originally based on?
And note that no RHEL5 user is going to be using a .36 kernel on their system, that's a completely unsupported and unadvised situation. ?Heck, I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?

Quoted 6 lines

I think some people do it internally, last time I did it was to test something I was backporting, so you want to make sure the upstream version boots and the backported version also boots on the same hw/userspace.
original kernel was 2.6.18.

Yes, that was the number, but does it really look anything like a .18 kernel.org release? :)

I'll test this out next week.

thanks,

greg k-h

Dave Airlie

2010-07-15 06:32 UTC #6 lore raw

Quoted 26 lines · Greg KH

Quoted 25 lines · Dave Airlie
Quoted 9 lines · Greg KH
Quoted 8 lines · Dave Airlie
Quoted 5 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Quoted 9 lines
Quoted 1 line
Also still used for booting mainline kernels on RHEL5 userspaces.
Really? ?I thought that was fixed a long time ago. ?What kernel was RHEL5 originally based on?
And note that no RHEL5 user is going to be using a .36 kernel on their system, that's a completely unsupported and unadvised situation. ?Heck, I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?
I think some people do it internally, last time I did it was to test something I was backporting, so you want to make sure the upstream version boots and the backported version also boots on the same hw/userspace.

Quoted 5 lines

Quoted 1 line
original kernel was 2.6.18.
Yes, that was the number, but does it really look anything like a .18 kernel.org release? :)

Well its more that the userspace is mostly what was released at the same time, we aren't going to update udev/mkinitrd unless some major problem was discovered.

Dave.

Greg KH

author

2010-07-15 07:55 UTC #7 lore raw

Quoted 29 lines · Dave Airlie

Quoted 28 lines · Greg KH
Quoted 26 lines · Dave Airlie
Quoted 9 lines · Greg KH
Quoted 8 lines · Dave Airlie
Quoted 5 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Quoted 9 lines
Quoted 1 line
Also still used for booting mainline kernels on RHEL5 userspaces.
Really? ?I thought that was fixed a long time ago. ?What kernel was RHEL5 originally based on?
And note that no RHEL5 user is going to be using a .36 kernel on their system, that's a completely unsupported and unadvised situation. ?Heck, I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?
I think some people do it internally, last time I did it was to test something I was backporting, so you want to make sure the upstream version boots and the backported version also boots on the same hw/userspace.
original kernel was 2.6.18.

Quoted 7 lines

Quoted 3 lines
Yes, that was the number, but does it really look anything like a .18 kernel.org release? ?:)
Well its more that the userspace is mostly what was released at the same time, we aren't going to update udev/mkinitrd unless some major problem was discovered.

That's fine, I can provide an updated package for those looney users that want to run this type of system :)

But ideally, I can figure out what is being needed and possibly reduce the footprint that is currently covered by this config option.

thanks,

greg k-h

Eric W. Biederman

2010-07-15 00:40 UTC #8 lore raw

In reply to Andrew Morton

Quoted 21 lines · Andrew Morton

Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set

Quoted 1 line

and the box still won't boot.

The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.

What is more interesting is that currently there is a bug in 2.6.35-rc5 where rmmod <netdriver> modprobe <netdriver> will in fact fail. There was an inadvertent regression and no one has noticed or complained. I spotted it by code review just a little bit ago and I haven't had a chance to write and test the fix yet.

If the code is going to start bitrotting and no one is going to notice or care simply removing the code instead of subjecting users to weird unexpected breakage seems like a responsible thing to do.

Eric

Greg KH

author

2010-07-15 04:15 UTC #9 lore raw

Quoted 23 lines · Eric W. Biederman

Quoted 21 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set

Quoted 5 lines

Quoted 1 line
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.

Anyone happen to know which tool it is? I remember we had had issues with FC3 around this area, but I thought we resolved them, so it's supprising to me that FC6 has issues.

Quoted 9 lines

What is more interesting is that currently there is a bug in 2.6.35-rc5 where rmmod <netdriver> modprobe <netdriver> will in fact fail. There was an inadvertent regression and no one has noticed or complained. I spotted it by code review just a little bit ago and I haven't had a chance to write and test the fix yet.
If the code is going to start bitrotting and no one is going to notice or care simply removing the code instead of subjecting users to weird unexpected breakage seems like a responsible thing to do.

Yeah, that's what prompted this removal. After the s390 guys said that they were all good to go, I figured no one else would have problems with it :)

If it turns out there still are issues with older userspaces like FC6 that we can't resolve, I have no problem dropping this patch and then we will have to fix up the regression.

thanks,

greg k-h

Eric W. Biederman

2010-07-15 04:29 UTC #10 lore raw

Quoted 30 lines · Greg KH

Quoted 23 lines · Eric W. Biederman
Quoted 21 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set
Quoted 5 lines
Quoted 1 line
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.

Quoted 3 lines

Anyone happen to know which tool it is? I remember we had had issues with FC3 around this area, but I thought we resolved them, so it's supprising to me that FC6 has issues.

It was something in the initrd, that didn't like the symlinks. It has been a year or more since I looked at it. At that point I just enabled SYSFS_DEPRECATED and moved on.

Quoted 10 lines

Quoted 9 lines
What is more interesting is that currently there is a bug in 2.6.35-rc5 where rmmod <netdriver> modprobe <netdriver> will in fact fail. There was an inadvertent regression and no one has noticed or complained. I spotted it by code review just a little bit ago and I haven't had a chance to write and test the fix yet.
If the code is going to start bitrotting and no one is going to notice or care simply removing the code instead of subjecting users to weird unexpected breakage seems like a responsible thing to do.

Quoted 7 lines

Yeah, that's what prompted this removal. After the s390 guys said that they were all good to go, I figured no one else would have problems with it :)
If it turns out there still are issues with older userspaces like FC6 that we can't resolve, I have no problem dropping this patch and then we will have to fix up the regression.

I still have to test it but it looks like a one liner. Actually two lines now that I have to fix the error in symlink creation as well.

Eric

Greg KH

author

2010-07-15 04:43 UTC #11 lore raw

Quoted 32 lines · Eric W. Biederman

Quoted 30 lines · Greg KH
Quoted 28 lines · Eric W. Biederman
Quoted 21 lines · Andrew Morton
Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set
Quoted 1 line
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.

Quoted 7 lines

Quoted 3 lines
Anyone happen to know which tool it is? I remember we had had issues with FC3 around this area, but I thought we resolved them, so it's supprising to me that FC6 has issues.
It was something in the initrd, that didn't like the symlinks. It has been a year or more since I looked at it. At that point I just enabled SYSFS_DEPRECATED and moved on.

If it was just the symlinks for the block devices, we might be able to reduce the amount of code hanging around. When I return from Europe next week, I'll try to dig into this.

Quoted 14 lines

Quoted 14 lines
Quoted 9 lines
What is more interesting is that currently there is a bug in 2.6.35-rc5 where rmmod <netdriver> modprobe <netdriver> will in fact fail. There was an inadvertent regression and no one has noticed or complained. I spotted it by code review just a little bit ago and I haven't had a chance to write and test the fix yet.
If the code is going to start bitrotting and no one is going to notice or care simply removing the code instead of subjecting users to weird unexpected breakage seems like a responsible thing to do.
Yeah, that's what prompted this removal. After the s390 guys said that they were all good to go, I figured no one else would have problems with it :)

Quoted 6 lines

Quoted 3 lines
If it turns out there still are issues with older userspaces like FC6 that we can't resolve, I have no problem dropping this patch and then we will have to fix up the regression.
I still have to test it but it looks like a one liner. Actually two lines now that I have to fix the error in symlink creation as well.

Ah, that's good to hear, as I'm sure .35 will need this fix :)

thanks,

greg k-h

Konrad Rzeszutek Wilk

2010-07-15 13:29 UTC #12 lore raw

In reply to Eric W. Biederman

Quoted 6 lines

Quoted 2 lines
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.

It is not just nash. Also multipathd would fail (as it expects the /sys/scsi_host/..<something> in certain directories), and 'lsscsi'. There might be other tools that depend on libsysfs to be affected by this as well.

Oh, and I think 'udev' might have some trouble too - but not 100% certain about that.

Greg KH

2010-07-15 14:27 UTC #13 lore raw

Quoted 10 lines · Konrad Rzeszutek Wilk

Quoted 6 lines
Quoted 2 lines
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.
It is not just nash. Also multipathd would fail (as it expects the /sys/scsi_host/..<something> in certain directories), and 'lsscsi'. There might be other tools that depend on libsysfs to be affected by this as well.

No tool should use libsysfs, that code broke a _long_ time ago. Do you know of anything using it?

Quoted 2 lines

Oh, and I think 'udev' might have some trouble too - but not 100% certain about that.

Heh, no udev works just fine :)

So basically, it's just the block links that are being affected, so that might let me narrow down the code covered by the depreciated option.

thanks,

greg k-h

Douglas Gilbert

2010-07-15 16:24 UTC #14 lore raw

In reply to Konrad Rzeszutek Wilk

Quoted 10 lines · Konrad Rzeszutek Wilk

Quoted 6 lines
Quoted 2 lines
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.
It is not just nash. Also multipathd would fail (as it expects the /sys/scsi_host/..<something> in certain directories), and 'lsscsi'. There might be other tools that depend on libsysfs to be affected by this as well.

lsscsi has been "CONFIG_SYSFS_DEPRECATED_V2" tolerant since version 0.21 released 20080710. The current version is 0.23 released 20091201 which will soon be displaced by 0.24 to cope with the most recent breakages.

Writing a user space tool that relies on sysfs structure and contents, stable over the whole lk 2.6 series, is impossible. For a history of my pain with lsscsi see its ChangeLog.

Happily most of my tools are based on an ioctl! SG_IO was a suggestion from Joerg Schilling and has now found its way into most block devices. Now it has a new lease of life in the bsg driver.

Doug Gilbert

Greg KH

author

2010-07-15 17:01 UTC #15 lore raw

Quoted 18 lines · Douglas Gilbert

Quoted 10 lines · Konrad Rzeszutek Wilk
Quoted 6 lines
Quoted 2 lines
and the box still won't boot.
The reason FC6 doesn't boot is there is a userspace tool I believe in the initrd that cares about symlinks when it should not.
It is not just nash. Also multipathd would fail (as it expects the /sys/scsi_host/..<something> in certain directories), and 'lsscsi'. There might be other tools that depend on libsysfs to be affected by this as well.
lsscsi has been "CONFIG_SYSFS_DEPRECATED_V2" tolerant since version 0.21 released 20080710. The current version is 0.23 released 20091201 which will soon be displaced by 0.24 to cope with the most recent breakages.

Quoted 4 lines

Writing a user space tool that relies on sysfs structure and contents, stable over the whole lk 2.6 series, is impossible. For a history of my pain with lsscsi see its ChangeLog.

Yeah, I'd recommend using libudev for any new tools if you want to interact with sysfs. It's much easier than mucking around with it directly and will be future-proof as udev can handle a lot of changes to sysfs that other tools might not realize.

thanks,

greg k-h

Greg KH

author

2010-07-15 03:52 UTC #16 lore raw

In reply to Andrew Morton

Quoted 21 lines · Andrew Morton

Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set

Quoted 1 line

and the box still won't boot.

Ick, that sucks.

What kernel was FC6 based on originally?

Kay, I thought that Fedora had fixed the "can't find root" issue for this type of sysfs configuation a long time ago. Or was that something else for PPC that I am thinking of?

thanks,

greg k-h

Kay Sievers

2010-07-15 08:31 UTC #17 lore raw

Quoted 11 lines · Greg KH

Quoted 1 line · Andrew Morton
and the box still won't boot.
Ick, that sucks.
What kernel was FC6 based on originally?
Kay, I thought that Fedora had fixed the "can't find root" issue for this type of sysfs configuation a long time ago. Or was that something else for PPC that I am thinking of?

It was fixed, and it's weird bug in nash.

If Andrew is still doing the same thing as years ago, he does not update the initramfs image, he boots with the old original initramfs along with the new kernel. :)

It might be, that just dropping the entire initramfs, and let the kernel mount the rootfs, has a good chance to boot the box.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Andrew Morton

2010-07-15 08:36 UTC #18 lore raw

Quoted 13 lines · On Thu, 15 Jul 2010 10:31:15 +0200 Kay Sievers <[email protected]> wrote:

Quoted 11 lines · Greg KH
Quoted 1 line · Andrew Morton
and the box still won't boot.
Ick, that sucks.
What kernel was FC6 based on originally?
Kay, I thought that Fedora had fixed the "can't find root" issue for this type of sysfs configuation a long time ago. __Or was that something else for PPC that I am thinking of?

Quoted 5 lines

It was fixed, and it's weird bug in nash.
If Andrew is still doing the same thing as years ago, he does not update the initramfs image, he boots with the old original initramfs along with the new kernel. :)

I run

	VERS=$(make kernelrelease 2>/dev/null)
	<copy vmlinux>
	/sbin/new-kernel-pkg --mkinitrd --install

Kay Sievers

2010-07-15 08:51 UTC #19 lore raw

Quoted 21 lines · Andrew Morton

Quoted 13 lines · On Thu, 15 Jul 2010 10:31:15 +0200 Kay Sievers <[email protected]> wrote:
Quoted 11 lines · Greg KH
Quoted 1 line · Andrew Morton
and the box still won't boot.
Ick, that sucks.
What kernel was FC6 based on originally?
Kay, I thought that Fedora had fixed the "can't find root" issue for this type of sysfs configuation a long time ago. __Or was that something else for PPC that I am thinking of?
Quoted 5 lines
It was fixed, and it's weird bug in nash.
If Andrew is still doing the same thing as years ago, he does not update the initramfs image, he boots with the old original initramfs along with the new kernel. :)

Quoted 5 lines

I run
VERS=$(make kernelrelease 2>/dev/null)
<copy vmlinux>
/sbin/new-kernel-pkg --mkinitrd --install

Ah, I see.

It might be, that the fix only hit FC7, or Andrew did not install the updates. The original mail about the nash problem is here:
http://lkml.org/lkml/2007/6/7/209

Kay
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Greg KH

2010-07-23 12:39 UTC #20 lore raw

In reply to Andrew Morton

Quoted 21 lines · Andrew Morton

Quoted 2 lines · On Fri, 9 Jul 2010 11:54:50 -0700 Greg Kroah-Hartman <[email protected]> wrote:
This is no longer needed by any userspace tools, so it's safe to remove.
Makes my FC6 test box not boot - can't find /dev/root. Then when I go back to plain old mainline (2.6.35-rc5) and run `make oldconfig', the .config change sticks:
(quoted diff) +1 -2
@@ -106,8 +106,7 @@
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
 # CONFIG_CGROUPS is not set
-CONFIG_SYSFS_DEPRECATED=y
-CONFIG_SYSFS_DEPRECATED_V2=y
+# CONFIG_SYSFS_DEPRECATED_V2 is not set
 CONFIG_RELAY=y
 CONFIG_NAMESPACES=y
 # CONFIG_UTS_NS is not set

Quoted 1 line

and the box still won't boot.

Ok, for now, I've removed this patch from my tree, so you should not have any problem.

I'll go work on this later next week when I have some more time.

thanks,

greg k-h