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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sun, 28 Jul 2019 19:51:03 +0300
From:   Nikolay Aleksandrov <>
To:     syzbot <>,,,,,,,,,,,,,,,,
Subject: Re: memory leak in fdb_create

On 28/07/2019 17:20, syzbot wrote:
> syzbot has bisected this bug to:
> commit 04cf31a759ef575f750a63777cee95500e410994
> Author: Michael Ellerman <>
> Date:   Thu Mar 24 11:04:01 2016 +0000
>     ftrace: Make ftrace_location_range() global
> bisection log:
> start commit:   abf02e29 Merge tag 'pm-5.2-rc6' of git://
> git tree:       upstream
> final crash:
> console output:
> kernel config:
> dashboard link:
> syz repro:
> C reproducer:
> Reported-by:
> Fixes: 04cf31a759ef ("ftrace: Make ftrace_location_range() global")
> For information about bisection process see:

I see the problem, it'd happen if the multicast stats memory allocation fails on bridge
init then the fdb added due to the default vlan would remain and the bridge kmem cache
would be destroyed while not empty (you can even trigger a BUG because of that).
I'll post a patch shortly after running a few tests.


Powered by blists - more mailing lists