From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI, PCI, ISA: Fix memory leak when there is no IRQ in the ACPI subsystem.
Date: Tue, 18 Feb 2014 11:21:39 +0100 [thread overview]
Message-ID: <53033433.7080002@linaro.org> (raw)
In-Reply-To: <87065822.vfIc9IskHH@vostro.rjw.lan>
On 18.02.2014 02:02, Rafael J. Wysocki wrote:
> On Monday, February 10, 2014 02:00:11 PM Tomasz Nowicki wrote:
>> Whenever we register ISA interrupt or not, we need to free the IRQ routing
>> table entry.
>>
>> Signed-off-by: Tomasz Nowicki <tomasz.nowicki@linaro.org>
>> ---
>> drivers/acpi/pci_irq.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
>> index b0e31b6..6ec0f36 100644
>> --- a/drivers/acpi/pci_irq.c
>> +++ b/drivers/acpi/pci_irq.c
>> @@ -432,6 +432,7 @@ int acpi_pci_irq_enable(struct pci_dev *dev)
>> #endif
>> dev_warn(&dev->dev, "PCI INT %c: no GSI\n", pin_name(pin));
>>
>> + kfree(entry);
>
> If I'm not mistaken, entry is always NULL here, isn't it?
acpi_pci_link_allocate_irq() can return negative gsi even if entry !=
NULL. For that case we'd have memory leak.
>
>> return 0;
>> }
>>
>>
>
next prev parent reply other threads:[~2014-02-18 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:00 [PATCH 1/2] ACPI, PCI, ISA: Call ISA-specific code only for architectures which support ISA Tomasz Nowicki
2014-02-10 13:00 ` [PATCH 2/2] ACPI, PCI, ISA: Fix memory leak when there is no IRQ in the ACPI subsystem Tomasz Nowicki
2014-02-18 1:02 ` Rafael J. Wysocki
2014-02-18 10:21 ` Tomasz Nowicki [this message]
2014-02-18 15:26 ` Rafael J. Wysocki
2014-02-19 10:26 ` Tomasz Nowicki
2014-02-15 1:05 ` [PATCH 1/2] ACPI, PCI, ISA: Call ISA-specific code only for architectures which support ISA Rafael J. Wysocki
2014-02-19 10:28 ` Tomasz Nowicki
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=53033433.7080002@linaro.org \
--to=tomasz.nowicki@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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