Badness at fs/sysfs/symlink.c:82 during qeth initalization
in [Kernel]
|
Prev: blkiocg async support
Next: [PATCH] vmscan: stop meaningless loop iteration when no reclaimable slab
From: Eric W. Biederman on 9 Jul 2010 06:10 Sachin Sant <sachinp(a)in.ibm.com> writes: > With today's next(20100709) qeth interface fails to initialize > with following Badness message: > sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0 Is this with CONFIG_SYSFS_DEPRECATED set? I think I may have made my warning check a little extra strict. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Eric W. Biederman on 9 Jul 2010 06:40
Sachin Sant <sachinp(a)in.ibm.com> writes: > Eric W. Biederman wrote: >>> With today's next(20100709) qeth interface fails to initialize >>> with following Badness message: >>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0 >>> >> >> Is this with CONFIG_SYSFS_DEPRECATED set? >> >> I think I may have made my warning check a little extra strict. >> > Yes. > > CONFIG_SYSFS_DEPRECATED=y > CONFIG_SYSFS_DEPRECATED_V2=y Ugh. It looks like the warning is correct and I have a regression in 2.6.35 that was overlooked because I did not closely test CONIFG_SYSFS_DEPRECATED. I will see if I can cook up a proper patch shortly. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |