Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752266AbaF3WPP (ORCPT ); Mon, 30 Jun 2014 18:15:15 -0400 Received: from mga03.intel.com ([143.182.124.21]:2026 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751273AbaF3WPN (ORCPT ); Mon, 30 Jun 2014 18:15:13 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,577,1400050800"; d="scan'208";a="451794710" Date: Mon, 30 Jun 2014 16:15:01 -0600 (MDT) From: Keith Busch X-X-Sender: vmware@localhost.localdom To: David Rientjes cc: Keith Busch , linux-kernel@vger.kernel.org, Thomas Gleixner , x86@kernel.org Subject: Re: [PATCH] x86: ioapic: Fix irq_free_descs count In-Reply-To: Message-ID: References: <1404142271-18311-1-git-send-email-keith.busch@intel.com> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 30 Jun 2014, David Rientjes wrote: > On Mon, 30 Jun 2014, Keith Busch wrote: > >> Signed-off-by: Keith Busch >> Cc: Thomas Gleixner >> Cc: x86@kernel.org > > Acked-by: David Rientjes > > This is definitely a fix for "genirq: Provide generic hwirq allocation > facility", but the changelog doesn't describe what the problem is and the > title that this somehow fixes irq_free_descs() doesn't make any sense. My mistake, I used the component from the commit I bisected the bug down to. > It's the equivalent of just doing > > - irq_free_descs(from, cnt); > + irq_free_descs(from, i - from); > > I'd suggest the patch title be changed to > > genirq: Fix memory leak when calling irq_free_hwirqs() > > and the changelog state > > irq_free_hwirqs() always calls irq_free_descs() with a cnt == 0 which > makes it a no-op since the interrupt count to free is decremented in > itself. Yes, I like your suggestion. Should I submit a v2, or will maintainer replace the changelog? -- 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/