From: Toshiaki Makita <toshiaki.makita1@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org, makita.toshiaki@lab.ntt.co.jp
Subject: Re: new leaks in bridging code.
Date: Sun, 30 Mar 2014 11:28:21 +0900 [thread overview]
Message-ID: <1396146501.2182.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20140329210102.GA22516@redhat.com>
On Sat, 2014-03-29 at 17:01 -0400, Dave Jones wrote:
> yesterdays bridging changes introduced leaks in the exit paths..
>
The patch has nothing to do with this memory leak.
It has existed since br_allowed_ingress was introduced.
I'm working on fixing it.
http://marc.info/?t=139598775400004&r=1&w=2
Thanks,
Toshiaki Makita
next prev parent reply other threads:[~2014-03-30 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <533730f2396e8_1c4bb46874192e@209.249.196.67.mail>
2014-03-29 21:01 ` new leaks in bridging code Dave Jones
2014-03-30 2:28 ` Toshiaki Makita [this message]
2014-03-30 2:47 ` Dave Jones
2014-03-31 3:54 ` Toshiaki Makita
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=1396146501.2182.5.camel@localhost.localdomain \
--to=toshiaki.makita1@gmail.com \
--cc=davej@redhat.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@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).