lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 29 Dec 2020 14:32:21 +0000 From: Mark Brown <broonie@...nel.org> To: Xiaolei Wang <xiaolei.wang@...driver.com> Cc: linux-kernel@...r.kernel.org, david@...hnology.com, gregkh@...uxfoundation.org, rafael@...nel.org Subject: Re: [PATCH v3] regmap: debugfs: Fix a memory leak when calling regmap_attach_dev On Tue, 29 Dec 2020 18:50:46 +0800, Xiaolei Wang wrote: > After initializing the regmap through > syscon_regmap_lookup_by_compatible, then regmap_attach_dev to the > device, because the debugfs_name has been allocated, there is no > need to redistribute it again > > unreferenced object 0xd8399b80 (size 64): > comm "swapper/0", pid 1, jiffies 4294937641 (age 278.590s) > hex dump (first 32 bytes): > 64 75 6d 6d 79 2d 69 6f 6d 75 78 63 2d 67 70 72 > dummy-iomuxc-gpr > 40 32 30 65 34 30 30 30 00 7f 52 5b d8 7e 42 69 > @20e4000..R[.~Bi > backtrace: > [<ca384d6f>] kasprintf+0x2c/0x54 > [<6ad3bbc2>] regmap_debugfs_init+0xdc/0x2fc > [<bc4181da>] __regmap_init+0xc38/0xd88 > [<1f7e0609>] of_syscon_register+0x168/0x294 > [<735e8766>] device_node_get_regmap+0x6c/0x98 > [<d96c8982>] imx6ul_init_machine+0x20/0x88 > [<0456565b>] customize_machine+0x1c/0x30 > [<d07393d8>] do_one_initcall+0x80/0x3ac > [<7e584867>] kernel_init_freeable+0x170/0x1f0 > [<80074741>] kernel_init+0x8/0x120 > [<285d6f28>] ret_from_fork+0x14/0x20 > [<00000000>] 0x0 Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next Thanks! [1/1] regmap: debugfs: Fix a memory leak when calling regmap_attach_dev commit: cffa4b2122f5f3e53cf3d529bbc74651f95856d5 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
Powered by blists - more mailing lists