Hi, Borislav On 12/02/2015 02:13 PM, Borislav Petkov wrote: > On Wed, Dec 02, 2015 at 02:01:55PM +0100, Michael Wang wrote: >> Yeah.. it's a little complicated since we have our own kernel tree and this >> won't be a problem for us, but we really prefer to help fix it in mainline >> too, as long as this is really a defect, so others could save time on >> research >> in future. > > Well, to keep it realistic and if it were me, I wouldn't even take such > a fix as it is apparently kmemleak's problem.
Do you mean this could be a real kmemleak? Could you please provide more details? > > So you could fix your testing instead to ignore that error message now > that you know it is a false-positive. That should be easiest. > Yeah, but it would be better to solve it, otherwise whoever saw this report will need to go into the amd-iommu, make sure it's not a real leak, then change their testing script... Regards, Michael Wang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
