From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] shared/gatt: Fix NULL dereference
Date: Mon, 22 Dec 2014 13:32:56 +0200 [thread overview]
Message-ID: <20141222113251.GA25294@aemeltch-MOBL1> (raw)
In-Reply-To: <1418981124-19877-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
ping
On Fri, Dec 19, 2014 at 11:25:23AM +0200, Andrei Emeltchenko wrote:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> The which is executed after checking (!op) is dereferencing op in
> function discovery_op_free().
> ---
> src/shared/gatt-client.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/src/shared/gatt-client.c b/src/shared/gatt-client.c
> index f7a90d1..c9fb05d 100644
> --- a/src/shared/gatt-client.c
> +++ b/src/shared/gatt-client.c
> @@ -1075,11 +1075,12 @@ static void process_service_changed(struct bt_gatt_client *client,
> return;
> }
>
> + discovery_op_free(op);
> +
> fail:
> util_debug(client->debug_callback, client->debug_data,
> "Failed to initiate service discovery"
> " after Service Changed");
> - discovery_op_free(op);
> }
>
> static void service_changed_cb(uint16_t value_handle, const uint8_t *value,
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-22 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 9:25 [PATCH 1/2] shared/gatt: Fix NULL dereference Andrei Emeltchenko
2014-12-19 9:25 ` [PATCH 2/2] tools/gatt: Fix not checking malloc() failure Andrei Emeltchenko
2014-12-22 11:32 ` Andrei Emeltchenko [this message]
2015-01-08 14:20 ` [PATCH 1/2] shared/gatt: Fix NULL dereference Andrei Emeltchenko
2015-01-09 9:45 ` Johan Hedberg
-- strict thread matches above, loose matches on Subject: below --
2014-12-05 7:30 Andrei Emeltchenko
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=20141222113251.GA25294@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@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