summaryrefslogtreecommitdiffstats
path: root/kernel/params.c
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2020-07-09 17:42:44 -0700
committerDavid S. Miller <davem@davemloft.net>2020-07-10 13:54:00 -0700
commita2b992c828f7651db369ba8f0eb0818d70232636 (patch)
treef66e1c6eeb40d7acf38ad802e80df4efdde2e2f3 /kernel/params.c
parent8fb49c0109f47e4a25e8ba36abd8381afbfa7a08 (diff)
downloadlinux-stable-a2b992c828f7651db369ba8f0eb0818d70232636.tar.gz
linux-stable-a2b992c828f7651db369ba8f0eb0818d70232636.tar.bz2
linux-stable-a2b992c828f7651db369ba8f0eb0818d70232636.zip
debugfs: make sure we can remove u32_array files cleanly
debugfs_create_u32_array() allocates a small structure to wrap the data and size information about the array. If users ever try to remove the file this leads to a leak since nothing ever frees this wrapper. That said there are no upstream users of debugfs_create_u32_array() that'd remove a u32 array file (we only have one u32 array user in CMA), so there is no real bug here. Make callers pass a wrapper they allocated. This way the lifetime management of the wrapper is on the caller, and we can avoid the potential leak in debugfs. CC: Chucheng Luo <luochucheng@vivo.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/params.c')
0 files changed, 0 insertions, 0 deletions