From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<lars@metafoo.de>, <hdegoede@redhat.com>,
<andriy.shevchenko@linux.intel.com>, <ddvlad@gmail.com>
Subject: Re: [PATCH v2] iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove
Date: Thu, 28 Oct 2021 14:51:47 +0100 [thread overview]
Message-ID: <20211028145147.7ad93c5f@jic23-huawei> (raw)
In-Reply-To: <20211025124159.2700301-1-yangyingliang@huawei.com>
On Mon, 25 Oct 2021 20:41:59 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:
> When ACPI type is ACPI_SMO8500, the data->dready_trig will not be set, the
> memory allocated by iio_triggered_buffer_setup() will not be freed, and cause
> memory leak as follows:
>
> unreferenced object 0xffff888009551400 (size 512):
> comm "i2c-SMO8500-125", pid 911, jiffies 4294911787 (age 83.852s)
> hex dump (first 32 bytes):
> 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 20 e2 e5 c0 ff ff ff ff ........ .......
> backtrace:
> [<0000000041ce75ee>] kmem_cache_alloc_trace+0x16d/0x360
> [<000000000aeb17b0>] iio_kfifo_allocate+0x41/0x130 [kfifo_buf]
> [<000000004b40c1f5>] iio_triggered_buffer_setup_ext+0x2c/0x210 [industrialio_triggered_buffer]
> [<000000004375b15f>] kxcjk1013_probe+0x10c3/0x1d81 [kxcjk_1013]
>
> Fix it by remove data->dready_trig condition in probe and remove.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Fixes: a25691c1f967 ("iio: accel: kxcjk1013: allow using an external trigger")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Applied to the fixes-togreg branch of iio.git. Note this will hit mainline after the merge window
now. Also, we should look at taking this driver fully over to devm managed functions.
Looks easy to do and would have avoided this particular leak.
Jonathan
> ---
> v2:
> drop some calltrace in commit message
> ---
> drivers/iio/accel/kxcjk-1013.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
> index a51fdd3c9b5b..24c9387c2968 100644
> --- a/drivers/iio/accel/kxcjk-1013.c
> +++ b/drivers/iio/accel/kxcjk-1013.c
> @@ -1595,8 +1595,7 @@ static int kxcjk1013_probe(struct i2c_client *client,
> return 0;
>
> err_buffer_cleanup:
> - if (data->dready_trig)
> - iio_triggered_buffer_cleanup(indio_dev);
> + iio_triggered_buffer_cleanup(indio_dev);
> err_trigger_unregister:
> if (data->dready_trig)
> iio_trigger_unregister(data->dready_trig);
> @@ -1618,8 +1617,8 @@ static int kxcjk1013_remove(struct i2c_client *client)
> pm_runtime_disable(&client->dev);
> pm_runtime_set_suspended(&client->dev);
>
> + iio_triggered_buffer_cleanup(indio_dev);
> if (data->dready_trig) {
> - iio_triggered_buffer_cleanup(indio_dev);
> iio_trigger_unregister(data->dready_trig);
> iio_trigger_unregister(data->motion_trig);
> }
prev parent reply other threads:[~2021-10-28 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 12:41 Yang Yingliang
2021-10-28 13:51 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211028145147.7ad93c5f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ddvlad@gmail.com \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®