Date: Wed, 2 Dec 2015 14:13:00 +0100
From: Borislav Petkov <bp@alien8.de>
To: Michael Wang <yun.wang@profitbricks.com>
Cc: Joerg Roedel <joro@8bytes.org>,
        Catalin Marinas <catalin.marinas@gmail.com>,
        iommu@lists.linux-foundation.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2] iommu/amd: gray the 'irq_remap_table' object for
 kmemleak
Message-ID: <20151202131300.GC3910@pd.tnic>
References: <5655D072.1000901@profitbricks.com>
 <565EC9F4.2050401@profitbricks.com>
 <CAHkRjk5QNQiNeJTcjKFQzpac_4us_3Ts1w4+uRw6TY16LbgsJA@mail.gmail.com>
 <565ECE54.5080706@profitbricks.com>
 <CAHkRjk5WzPT1gRaa=3qyrp1gcee9ZQKF_rU42FAu0C6ep8JPug@mail.gmail.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=utf-8
Content-Disposition: inline
In-Reply-To: <565EEBC3.5050807@profitbricks.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 887
Lines: 22

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/