These patches solve two lingering memory leak scenarios introduced in tidspbridge code. 1. Due to missing balanced calls during bridge_release deallocation, and a potential leak in bridge_open because of missing cleanup path. 2. Leaks because of a misuse of an already freed pointer, which triggered error paths during module removal leaking some memory. When accepted they must be propagated to stable kernel releases. Omar Ramirez Luna (2): staging: tidspbridge: fix bridge_open memory leaks staging: tidspbridge: fix incorrect free to drv_datap drivers/staging/tidspbridge/core/tiomap3430.c | 2 - drivers/staging/tidspbridge/rmgr/drv_interface.c | 58 +++++++++++++--------- 2 files changed, 35 insertions(+), 25 deletions(-) -- 1.7.4.1 _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
