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
Subject: Re: [B.A.T.M.A.N.] Memory leakage
Date: Fri, 19 May 2017 09:07:04 +0200	[thread overview]
Message-ID: <1661470.hcNBASnkvL@bentobox> (raw)
In-Reply-To: <OFE5F92E4D.60A86F64-ONC1258125.00232B05-C1258125.0023A966@phoenixcontact.com>

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

On Freitag, 19. Mai 2017 08:29:29 CEST Andreas Pape wrote:
[...]
> I think the line with the "return NET_RX_DROP;" needs to be replaced by
> "goto skb_free;".

Yes

> How is the correct procedure to change this? As this patch has already
> been committed to
> the git repo I guess I should send a new patch or is a new version of the
> old patch necessary?

Thanks for debugging this. Please sent a new patch based on master [1] and add 
following line above your Signed-off-by

    Fixes: bfe2a1971f43 ("batman-adv: drop unicast packets from other backbone gw")

We will take care of submitting it to Linux net for Linux 4.12. If you still
have problems with your IT department then you can either send the patch from 
a private mail account (git-send-email will then add an extra "From:" line to 
keep your phoenixcontact.com mail address as author mail address) or (if not
otherwise possible) sent it again as attachment to me or Simon. We can then
forward it to the mailing list.

Kind regards,
	Sven

[1] Your patch is currently only in master. It should actually be in maint but
    Simon hadn't found the time to release master as 2017.1. Which is not to
    bad because now we can still incorporate your fix.
    It would be different when the patch would already be part of maint. Then
    it would be better when you should create your patch on top of maint

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

      reply	other threads:[~2017-05-19  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  6:29 [B.A.T.M.A.N.] Memory leakage Andreas Pape
2017-05-19  7:07 ` Sven Eckelmann [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=1661470.hcNBASnkvL@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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