Quoting Lionel Landwerlin (2017-08-04 09:56:36) > Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@xxxxxxxxx> > > I'm curious though, why hasn't it been a problem before?? > All of the configs we store in kernel don't seem to properly initialize > attr either, yet it hasn't yield any warning. > Did we get it wrong all along there too? The attr contains an embedded lock_class, but due to the design of lockdep all lock_classes must be static. sysfs_attr_init() contains a magic static lock_class - so instead of each attr now being an independent lock class, all of the dynamic attr belong to the same class. Don't try to use sysfs of one attr from inside the callback of another! -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
