Hi Dmitry: On Thu, Feb 21, 2019 at 11:54:42AM +0100, Dmitry Vyukov wrote: > > Taking into account that this still happened only once, I tend to > write it off onto a previous silent memory corruption (we have dozens > of known bugs that corrupt memory). So if several people already > looked at it and don't see the root cause, it's probably time to stop > spending time on this until we have more info. > > Although, there was also this one: > https://groups.google.com/d/msg/syzkaller-bugs/QfCCSxdB1aM/y2cn9IZJCwAJ > I have not checked if it can be the root cause of this report, but it > points suspiciously close to this stack and when I looked at it, it > the report looked legit. Have you had any more reports of this kind coming from br_multicast? It looks like ommit 1515a63fc413f160d20574ab0894e7f1020c7be2 Author: Nikolay Aleksandrov <nikolay@xxxxxxxxxxxxxxxxxxx> Date: Wed Apr 3 23:27:24 2019 +0300 net: bridge: always clear mcast matching struct on reports and leaves may have at least fixed the uninitialised value error. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
