netdev - Re: new leaks in bridging code.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140330024709.GA25793@redhat.com>
Date:	Sat, 29 Mar 2014 22:47:09 -0400
From:	Dave Jones <davej@...hat.com>
To:	Toshiaki Makita <toshiaki.makita1@...il.com>
Cc:	netdev@...r.kernel.org, makita.toshiaki@....ntt.co.jp
Subject: Re: new leaks in bridging code.

On Sun, Mar 30, 2014 at 11:28:21AM +0900, Toshiaki Makita wrote:
 > 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.

Good point, the checker only picked up it as 'new' because of the
additional call to vlan_untag.

 > It has existed since br_allowed_ingress was introduced.
 > I'm working on fixing it.
 > http://marc.info/?t=139598775400004&r=1&w=2

Great! (I'm behind on email so hadn't seen this thread).

Thanks,

	Dave

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html