From: Johan Hedberg <johan.hedberg@gmail.com>
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org,
Lucas De Marchi <lucas.de.marchi@gmail.com>
Subject: Re: [PATCH BlueZ] core: Fix walking the list while removing elements
Date: Thu, 4 Oct 2012 21:22:23 +0300 [thread overview]
Message-ID: <20121004182223.GA22857@x220.P-661HNU-F1> (raw)
In-Reply-To: <1349370439-6345-1-git-send-email-lucas.demarchi@profusion.mobi>
Hi Lucas,
On Thu, Oct 04, 2012, Lucas De Marchi wrote:
> If we are walking a GSList and remove the element we are pointing to,
> the next iteration g_slist_next() will access previously freed
> memory.
> ---
> src/device.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied. Thanks.
Johan
next prev parent reply other threads:[~2012-10-04 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:07 [PATCH BlueZ] core: Fix walking the list while removing elements Lucas De Marchi
2012-10-04 17:16 ` Bastien Nocera
2012-10-04 17:21 ` Lucas De Marchi
2012-10-04 17:30 ` Bastien Nocera
2012-10-04 18:22 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-04 6:06 Lucas De Marchi
2012-10-04 7:49 ` Johan Hedberg
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=20121004182223.GA22857@x220.P-661HNU-F1 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@profusion.mobi \
/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