From: Keith Busch <keith.busch@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: Keith Busch <keith.busch@intel.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org
Subject: Re: [PATCH] x86: ioapic: Fix irq_free_descs count
Date: Mon, 30 Jun 2014 16:15:01 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1406301613100.4699@AMR> (raw)
In-Reply-To: <alpine.DEB.2.02.1406301452060.13545@chino.kir.corp.google.com>
On Mon, 30 Jun 2014, David Rientjes wrote:
> On Mon, 30 Jun 2014, Keith Busch wrote:
>
>> Signed-off-by: Keith Busch <keith.busch@intel.com>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: x86@kernel.org
>
> Acked-by: David Rientjes <rientjes@google.com>
>
> 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?
next prev parent reply other threads:[~2014-06-30 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:31 Keith Busch
2014-06-30 21:57 ` David Rientjes
2014-06-30 22:15 ` Keith Busch [this message]
2014-06-30 22:19 ` David Rientjes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.03.1406301613100.4699@AMR \
--to=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®