2011/4/12 Greg KH <greg@xxxxxxxxx>: > On Tue, Apr 12, 2011 at 12:45:33AM +0200, RafaÅ MiÅecki wrote: >> 2011/4/12 Greg KH <greg@xxxxxxxxx>: >> > On Tue, Apr 12, 2011 at 12:12:47AM +0200, RafaÅ MiÅecki wrote: >> >> 2011/4/11 Greg KH <greg@xxxxxxxxx>: >> >> > On Mon, Apr 11, 2011 at 11:36:39PM +0200, RafaÅ MiÅecki wrote: >> >> >> 2011/4/11 Greg KH <greg@xxxxxxxxx>: >> >> >> > Please read the documentation for how to do this properly. ÂI find it >> >> >> > really hard to believe that you wrote that comment instead of putting in >> >> >> > the 2 lines of code required for this function. >> >> >> > >> >> >> > Especially as-it-is, your code does not work properly and leaks memory >> >> >> > badly. ÂWhy would you do that on purpose? >> >> >> >> >> >> I tried to read some documentation about this. >> >> >> >> >> >> 1) driver-mode/device.txt says only that: >> >> >> > Callback to free the device after all references have >> >> >> > gone away. This should be set by the allocator of the >> >> >> > device (i.e. the bus driver that discovered the device). >> >> >> I *really* do not know how my driver should "free" core on AXI bus. >> >> > >> >> > The structure that you have created, added to the bus, is now ready to >> >> > have its memory freed. ÂSo free it. >> >> > >> >> > This usually means something like: >> >> > Â Â Â Âstruct my_obj = to_my_obj(dev); >> >> > Â Â Â Âkfree(my_obj); >> >> > in the release function. >> >> >> >> I register core->dev to the bus (I set core->dev.bus and >> >> core->dev.parent, is that what you mean?). This core->dev is "struct >> >> dev" embedded in "struct axi_device". By embedded I mean it is *not* a >> >> pointer, I do not alloc it, it's part of the "struct axi_device". >> > >> > That is exactly as it should be. >> > >> > Then in your release function, free the struct axi_device. ÂIt's that >> > simple. ÂTo try to free it before then would be wrong and cause >> > problems. >> >> This is because it is defined as: >> struct axi_device cores[AXI_MAX_NR_CORES]; > > No way, seriously? > > You can't do that, no static struct devices please. ÂMake these dynamic > and everything will be fine. ÂThe -mm tree used to have a huge warning > if you ever tried to register a statically allocated struct, but that > didn't really work out, but would have saved you a lot of time here, > sorry. > > So dynamically allocate the structures and you will be fine. Well, I saw that along kernel, I had no idea there is anything wrong about this. It seems more ppl do not know about this: struct radeon_ib ibs[RADEON_IB_POOL_SIZE]; struct radeon_pm_clock_info clock_info[8]; struct radeon_pm_profile profiles[PM_PROFILE_MAX]; struct radeon_surface_reg surface_regs[RADEON_GEM_MAX_SURFACES]; struct radeon_i2c_chan *i2c_bus[RADEON_MAX_I2C_BUS]; struct b43_key key[B43_NR_GROUP_KEYS * 2 + B43_NR_PAIRWISE_KEYS]; struct ssb_device devices[SSB_MAX_NR_CORES]; I guess I could fine more examples by simple grepping .h files. Is there some guide around with things like this we should avoid? checkpatch does no catch this, so maybe just some manual? Could you point me to it? -- RafaÅ _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
