From: patchwork-bot+chrome-platform@kernel.org
To: Rustam Subkhankulov <subkhankulov@ispras.ru>
Cc: bleung@chromium.org, dmitry.torokhov@gmail.com,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
khoroshilov@ispras.ru, ldv-project@linuxtesting.org
Subject: Re: [PATCH] platform/chrome: fix double-free in chromeos_laptop_prepare()
Date: Mon, 22 Aug 2022 07:00:15 +0000 [thread overview]
Message-ID: <166115161516.13978.12007993909417445952.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220813220843.2373004-1-subkhankulov@ispras.ru>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Sun, 14 Aug 2022 01:08:43 +0300 you wrote:
> If chromeos_laptop_prepare_i2c_peripherals() fails after allocating memory
> for 'cros_laptop->i2c_peripherals', this memory is freed at 'err_out' label
> and nonzero value is returned. Then chromeos_laptop_destroy() is called,
> resulting in double-free error.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> [...]
Here is the summary with links:
- platform/chrome: fix double-free in chromeos_laptop_prepare()
https://git.kernel.org/chrome-platform/c/6ad4194d6a1e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-22 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 22:08 [PATCH] platform/chrome: fix double-free in chromeos_laptop_prepare() Rustam Subkhankulov
2022-08-15 5:00 ` Tzung-Bi Shih
2022-08-20 17:05 ` Rustam Subkhankulov
2022-08-21 4:51 ` Dmitry Torokhov
2022-08-22 6:40 ` Tzung-Bi Shih
2022-08-22 7:00 ` patchwork-bot+chrome-platform [this message]
2022-08-24 2:20 ` patchwork-bot+chrome-platform
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=166115161516.13978.12007993909417445952.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=subkhankulov@ispras.ru \
/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