From: Greg KH <greg@kroah.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Simon Kirby <sim@hostway.ca>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] x86/PCI: fix boot-time memory leak
Date: Mon, 17 Oct 2011 13:21:45 -0700 [thread overview]
Message-ID: <20111017202145.GA6861@kroah.com> (raw)
In-Reply-To: <CAErSpo4fo+qJei5XeCqWd3kK7h=EPVtpuP0K5EvicCwnheMG5A@mail.gmail.com>
On Mon, Oct 17, 2011 at 01:59:10PM -0600, Bjorn Helgaas wrote:
> On Mon, Oct 17, 2011 at 1:46 PM, Greg KH <greg@kroah.com> wrote:
> > On Mon, Oct 17, 2011 at 01:40:37PM -0600, Bjorn Helgaas wrote:
> >> From: Catalin Marinas <catalin.marinas@arm.com>
> >>
> >> If we're not using _CRS, the host bridge's bus name and resource structures
> >> were allocated but never freed. This patch fixes that.
> >>
> >> Reported-by: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
> >> Reported-by: Simon Kirby <sim@hostway.ca>
> >> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> >
> > Is this something for the 3.0-stable tree as well?
>
> It could be applied to 3.0-stable, but it only fixes a boot-time leak
> of a couple hundred bytes (approx 16-byte name + typically 4 56-byte
> struct resources), so I don't think it qualifies as any kind of a
> critical fix.
Ok, just wanted to check, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-17 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 19:40 [PATCH] x86/PCI: fix boot-time memory leak Bjorn Helgaas
2011-10-17 19:46 ` Greg KH
2011-10-17 19:59 ` Bjorn Helgaas
2011-10-17 20:21 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-23 16:59 Bjorn Helgaas
2011-10-17 16:30 ` Bjorn Helgaas
2011-10-17 19:17 ` Yinghai Lu
2011-10-17 21:04 ` Catalin Marinas
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=20111017202145.GA6861@kroah.com \
--to=greg@kroah.com \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sim@hostway.ca \
--cc=tglx@linutronix.de \
/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