From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Jiri Kosina <jkosina@suse.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
sre@kernel.org, linux-pm@vger.kernel.org,
"H.J. Lu" <hjl.tools@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] HID: hid-input: Fix accessing freed memory during device disconnect
Date: Mon, 03 Aug 2015 13:57:55 +0900 [thread overview]
Message-ID: <55BEF4D3.7050903@samsung.com> (raw)
In-Reply-To: <1438560081-23055-1-git-send-email-k.kozlowski@samsung.com>
On 03.08.2015 09:01, Krzysztof Kozlowski wrote:
> During unbinding the driver was dereferencing a pointer to memory
> already freed by power_supply_unregister().
>
> Driver was freeing its internal description of battery through pointers
> stored in power_supply structure. However, because the core owns the
> power supply instance, after calling power_supply_unregister() this
> memory is freed and the driver cannot access these members.
>
> Fix this by storing the pointer to internal description of battery in a
> local variable before calling power_supply_unregister(), so the pointer
> remains valid.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Reported-by: H.J. Lu <hjl.tools@gmail.com>
> Fixes: 297d716f6260 ("power_supply: Change ownership from driver to core")
> Cc: <stable@vger.kernel.org>
>
> ---
> Changes since v1:
> 1. Re-work idea, use local variable instead of devm-like functions
> (pointed out by Dmitry Torokhov).
> 2. Adjusted subject and commit message.
I missed the warning:
drivers/hid/hid-input.c:470:11: warning: assignment discards �const�
qualifier from pointer target type
I'll fix this and send v3.
Best regards,
Krzysztof
prev parent reply other threads:[~2015-08-03 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 0:01 [PATCH v2] HID: hid-input: Fix accessing freed memory during device disconnect Krzysztof Kozlowski
2015-08-03 4:57 ` Krzysztof Kozlowski [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=55BEF4D3.7050903@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=jkosina@suse.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).