From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-iio@vger.kernel.org>, <jonathan.cameron@huawei.com>
Subject: Re: [PATCH] iio: trigger: sysfs: fix possible memory leak in iio_sysfs_trig_init()
Date: Sun, 23 Oct 2022 12:02:28 +0100 [thread overview]
Message-ID: <20221023120228.6719e888@jic23-huawei> (raw)
In-Reply-To: <20221022074212.1386424-1-yangyingliang@huawei.com>
On Sat, 22 Oct 2022 15:42:12 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:
> dev_set_name() allocates memory for name, it need be freed
> when device_add() fails, call put_device() to give up the
> reference that hold in device_initialize(), so that it can
> be freed in kobject_cleanup() when the refcount hit to 0.
>
> Fault injection test can trigger this:
>
> unreferenced object 0xffff8e8340a7b4c0 (size 32):
> comm "modprobe", pid 243, jiffies 4294678145 (age 48.845s)
> hex dump (first 32 bytes):
> 69 69 6f 5f 73 79 73 66 73 5f 74 72 69 67 67 65 iio_sysfs_trigge
> 72 00 a7 40 83 8e ff ff 00 86 13 c4 f6 ee ff ff r..@............
> backtrace:
> [<0000000074999de8>] __kmem_cache_alloc_node+0x1e9/0x360
> [<00000000497fd30b>] __kmalloc_node_track_caller+0x44/0x1a0
> [<000000003636c520>] kstrdup+0x2d/0x60
> [<0000000032f84da2>] kobject_set_name_vargs+0x1e/0x90
> [<0000000092efe493>] dev_set_name+0x4e/0x70
>
> Fixes: 1f785681a870 ("staging:iio:trigger sysfs userspace trigger rework.")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
> ---
> drivers/iio/trigger/iio-trig-sysfs.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/trigger/iio-trig-sysfs.c b/drivers/iio/trigger/iio-trig-sysfs.c
> index d6c5e9644738..6b05eed41612 100644
> --- a/drivers/iio/trigger/iio-trig-sysfs.c
> +++ b/drivers/iio/trigger/iio-trig-sysfs.c
> @@ -203,9 +203,13 @@ static int iio_sysfs_trigger_remove(int id)
>
> static int __init iio_sysfs_trig_init(void)
> {
> + int ret;
> device_initialize(&iio_sysfs_trig_dev);
> dev_set_name(&iio_sysfs_trig_dev, "iio_sysfs_trigger");
> - return device_add(&iio_sysfs_trig_dev);
> + ret = device_add(&iio_sysfs_trig_dev);
> + if (ret)
> + put_device(&iio_sysfs_trig_dev);
> + return ret;
> }
> module_init(iio_sysfs_trig_init);
>
prev parent reply other threads:[~2022-10-23 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 7:42 [PATCH] iio: trigger: sysfs: fix possible memory leak in iio_sysfs_trig_init() Yang Yingliang
2022-10-23 11:02 ` 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=20221023120228.6719e888@jic23-huawei \
--to=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-iio@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