public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org, Martin Weinelt <martin@linuxlounge.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: fix memory leak in in batadv_dat_put_dhcp
Date: Wed, 06 Feb 2019 19:38:41 +0100	[thread overview]
Message-ID: <1556071.oqAPsG2Tpi@sven-edge> (raw)
In-Reply-To: <mailman.2.1549464410.7610.b.a.t.m.a.n@lists.open-mesh.org>

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

On Wednesday, 6 February 2019 15.39.14 CET Martin Weinelt via B.A.T.M.A.N wrote:
> Consume the skb to avoid leaking memory.
> 
> Fixes: 1fd1ce2d383f ("batman-adv: Snoop DHCPACKs for DAT")
> Signed-off-by: Martin Weinelt <martin@linuxlounge.net>

Good catch. I've modified the commit message to make it better 
understandable and to describe the actual problem in more detail.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2019-02-06 18:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.2.1549464410.7610.b.a.t.m.a.n@lists.open-mesh.org>]

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=1556071.oqAPsG2Tpi@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=martin@linuxlounge.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