summaryrefslogtreecommitdiff
path: root/drivers/ddr/fsl/ddr1_dimm_params.c
diff options
context:
space:
mode:
authorPali Rohár <pali@kernel.org>2022-05-30 11:09:11 +0200
committerTom Rini <trini@konsulko.com>2022-07-08 09:05:47 -0400
commit69ca709d0fb001851f443b0b744c6d65bb6c22c1 (patch)
treef6a7c7a0fb49cd89317a65ade5aa4a296d81de15 /drivers/ddr/fsl/ddr1_dimm_params.c
parent54ee5ae84191aa7c53c9de709f6c66411d3e2dda (diff)
ubifs: Fix reference count leak in ubifsumount
Original ubifs code was designed that after ubifs_umount() call it is required to also call ubi_close_volume() which closes underlying UBI volume. But U-Boot ubifs modification have not implemented it properly which caused that ubifsumount command contains resource leak. It can be observed by calling simple sequence of commands: => ubi part mtd2 ubi0: attaching mtd2 ... => ubifsmount ubi0 => ubifsumount Unmounting UBIFS volume rootfs! => ubi detach ubi0 error: ubi_detach_mtd_dev: ubi0 reference count 1, destroy anyway ubi0: detaching mtd2 ubi0: mtd2 is detached Fix this issue by calling ubi_close_volume() and mutex_unlock() in directly in ubifs_umount() function before freeing U-Boot's global ubifs_sb. And remove duplicate calls of these two functions in remaining places. Note that when ubifs_umount() is not called then during error handling is still needed to call ubi_close_volume() and mutex_unlock. With this change ubifsumount command does not throw that error anymore: => ubi part rootfs ubi0: attaching mtd2 ... => ubifsmount ubi0 => ubifsumount Unmounting UBIFS volume rootfs! => ubi detach ubi0: detaching mtd2 ubi0: mtd2 is detached Signed-off-by: Pali Rohár <pali@kernel.org>
Diffstat (limited to 'drivers/ddr/fsl/ddr1_dimm_params.c')
0 files changed, 0 insertions, 0 deletions