From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: fix possible memleak in fragmentation
Date: Tue, 4 Jun 2013 17:31:35 +0800 [thread overview]
Message-ID: <201306041731.35269.lindner_marek@yahoo.de> (raw)
In-Reply-To: <51A450B4.9090901@hundeboll.net>
On Tuesday, May 28, 2013 14:37:40 Martin Hundebøll wrote:
> On 2013-05-28 08:23, Martin Hundebøll wrote:
> > Use a variable for return value in batadv_frag_insert_packet() to free
> > the allocated struct batadv_frag_list_entry in all cases where it is not
> > inserted into a chain.
>
> The possible memleak was introduced by
> 9b3eab61754d74a93c9840c296013fe3b4a1b606 ("batman-adv: Receive
> fragmented packets and merge")
Applied in revision 0b415bb.
Thanks,
Marek
prev parent reply other threads:[~2013-06-04 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 6:23 [B.A.T.M.A.N.] [PATCH] batman-adv: fix possible memleak in fragmentation Martin Hundebøll
2013-05-28 6:37 ` Martin Hundebøll
2013-06-04 9:31 ` Marek Lindner [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=201306041731.35269.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=martin@hundeboll.net \
/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