On Tue, 2015-11-03 at 09:48 +0100, Dmitry Vyukov wrote: > On Mon, Nov 2, 2015 at 8:01 PM, Eric W. Biederman <ebied...@xmission.com> > wrote: > > Dmitry Vyukov <dvyu...@google.com> writes: > > > >> Hello, > >> > >> I am hitting the following warnings on > >> bcee19f424a0d8c26ecf2607b73c690802658b29 (4.3): > > > > Do you have any trace of the earlier failures? > > > > This appears to be something caused by an earlier failure (possibly > > whatever fails to allocate memory). Having network devices present > > but being in the generic cleanup routines is wrong. > > > > If there is no additional information can you please rerun with the > > following change applied? That should at least report which function is > > failing, and give us a good clue where to start debugging this. > > > So is it all fixed now? Or it is still clear how it can happen? > Eric (Dumazet), do you see how the WARNING can fire? > I don't have any logs at the moment, but I can run fuzzer for longer > to reproduce it again if necessary.
No idea. I fixed a completely different bug I think, while simply looking at sit code, since your report mentioned a sit0 name. Namely a pure memory leak. We have hundred of old bugs yet to fix. Not counting the new ones that we'll add while fixing them. Feel free to run your fuzzer of course. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
