Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757988AbbLBLb0 (ORCPT ); Wed, 2 Dec 2015 06:31:26 -0500 Received: from mail-wm0-f52.google.com ([74.125.82.52]:34254 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757918AbbLBLbX (ORCPT ); Wed, 2 Dec 2015 06:31:23 -0500 MIME-Version: 1.0 In-Reply-To: <565ECE54.5080706@profitbricks.com> References: <564EFF6A.2050709@profitbricks.com> <564F051E.9010703@profitbricks.com> <20151125150806.GG2064@8bytes.org> <5655D072.1000901@profitbricks.com> <565EC9F4.2050401@profitbricks.com> <565ECE54.5080706@profitbricks.com> From: Catalin Marinas Date: Wed, 2 Dec 2015 11:31:02 +0000 Message-ID: Subject: Re: [RFC PATCH v2] iommu/amd: gray the 'irq_remap_table' object for kmemleak To: Michael Wang Cc: Joerg Roedel , iommu@lists.linux-foundation.org, Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1175 Lines: 26 On 2 December 2015 at 10:56, Michael Wang wrote: > On 12/02/2015 11:52 AM, Catalin Marinas wrote: >>> Is there any more concern? actually we just want to get rid of this >>> annoying report on obj won't leak, if you're going to create obj for >>> 'irq_lookup_table' that's also fine for us, or will you pick this patch? >> >> My preference (from a kmemleak perspective) is to tell kmemleak about >> the irq_lookup_table. Untested: > > I'm fine with both solution, will leave the decision to maintainer :-) > > BTW, could you please send a formal patch with descriptions? I could copy your description but I don't currently have a way (nor time) to test the patch. If you plan to test it anyway, please feel free to include my diff (which I guess was badly re-formatted by gmail), I don't really mind which author it is (I found it easier to show a diff than explain in plain English ;)). -- Catalin -- 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/