From: Johan Hedberg <johan.hedberg@gmail.com>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] shared/gatt: Fix NULL dereference
Date: Fri, 9 Jan 2015 11:45:56 +0200 [thread overview]
Message-ID: <20150109094556.GA7762@t440s.lan> (raw)
In-Reply-To: <1418981124-19877-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
On Fri, Dec 19, 2014, Andrei Emeltchenko wrote:
> 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(-)
Both patches in this set have been applied. Thanks.
Johan
next prev parent reply other threads:[~2015-01-09 9:45 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 ` [PATCH 1/2] shared/gatt: Fix NULL dereference Andrei Emeltchenko
2015-01-08 14:20 ` Andrei Emeltchenko
2015-01-09 9:45 ` Johan Hedberg [this message]
-- 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=20150109094556.GA7762@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).