diff options
author | Stephen Boyd <swboyd@chromium.org> | 2018-08-15 13:37:04 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-09-14 15:37:23 +0200 |
commit | 20edec388277b62ddfddb8b2b376a937a2cd6d1b (patch) | |
tree | c9c10a7332a80a78ecc5b754178ee97ea5917466 /block/blk-mq.c | |
parent | 09ed061a4f56d50758851ca3997510f27115f81b (diff) | |
download | linux-20edec388277b62ddfddb8b2b376a937a2cd6d1b.tar.bz2 |
firmware: coreboot: Unmap ioregion after device population
Both callers of coreboot_table_init() ioremap the pointer that comes in
but they don't unmap the memory on failure. Both of them also fail probe
immediately with the return value of coreboot_table_init(), leaking a
mapping when it fails. The mapping isn't necessary at all after devices
are populated either, so we can just drop the mapping here when we exit
the function. Let's do that to simplify the code a bit and plug the leak.
Cc: Wei-Ning Huang <wnhuang@chromium.org>
Cc: Julius Werner <jwerner@chromium.org>
Cc: Brian Norris <briannorris@chromium.org>
Cc: Samuel Holland <samuel@sholland.org>
Fixes: 570d30c2823f ("firmware: coreboot: Expose the coreboot table as a bus")
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block/blk-mq.c')
0 files changed, 0 insertions, 0 deletions