On Mon, May 10, 2010 at 02:54:40PM +0200, Balbi Felipe (Nokia-D/Helsinki) wrote: > On Mon, May 10, 2010 at 01:13:00PM +0200, ext Paul Mundt wrote: > >You'll still need the show function, but all of the rest of this is just > >duplicating what single_open() already does. If the socinfo string is > >static you may also want to rework this a bit so you can just stash the > >string in the proc_dir_entry private data. Combine this with something > >like kstrdup() and you'll save yourself a bit of stack while you're at > >it. > > doesn't ksrtdup() cause memleak ?? Or is it only when used with > module parameters ?? I'm not aware of the module parameter stuff.. but the leak might be other thing than kstrdup? > > -- > balbi > > DefectiveByDesign.org -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
