From: Borislav Petkov Subject: Re: [RFC PATCH v2] iommu/amd: gray the 'irq_remap_table' object for kmemleak Date: Wed, 2 Dec 2015 14:13:00 +0100 Message-ID: <20151202131300.GC3910@pd.tnic> References: <5655D072.1000901@profitbricks.com> <565EC9F4.2050401@profitbricks.com> <565ECE54.5080706@profitbricks.com> <565ED81B.3020606@profitbricks.com> <20151202115142.GD18805@8bytes.org> <565EE4AA.4070309@profitbricks.com> <20151202125315.GB3910@pd.tnic> <565EEBC3.5050807@profitbricks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <565EEBC3.5050807-EIkl63zCoXaH+58JC4qpiA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Michael Wang Cc: Linux Kernel Mailing List , iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Catalin Marinas List-Id: iommu@lists.linux-foundation.org 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. 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. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.