Upstream kernel memleak 5.10+? octeon-ethernet.ko

[Grommish]

@robimarko

I think you understood my reply wrong

I did, my apologizes! And yes, I agree.. If nothing I've learned from hanging around here, it's that "my local resources" aren't enough for what the kernel, OpenWrt, etc, actually does. The decisions I make locally are easy to justify when I look at it in the context of "I can build this" but are wholly unacceptable when scaled up to the sizes the kernel would to need to do to do it!

[flygarn12]

@robimarko

My point is that people always seem pissed when there is a regression or a bug found after X releases and are like "Why wasn't this found in testing, we need more testing, etc".
They think that there has got to be some huge testing and automation setup for everything, while the truth is that unless somebody notices the bug then it wont get caught, the more obscure the arch the lower the chance.

I would say we as users (more or less advanced) are the testers…

If everything had been tested to perfection we wouldn’t have any bugs anywhere. But we do have bugs, this was only one bug in the whole world of bugs.

[robimarko]

Yeah, you summed it up good.

[PolynomialDivision]

Don't forget to backport to 22.03.

[Grommish]

I believe @rsalvaterra is working on that, along with reverting the source-only tag.