The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Om Narasimhan" <om.turyx@gmail.com>
To: "Len Brown" <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@lists.osdl.org
Subject: Re: memory leak fix in acpi_memhotplug.c, kmalloc to kzalloc conversion.
Date: Sat, 26 Aug 2006 21:06:20 -0700	[thread overview]
Message-ID: <6b4e42d10608262106ibc44172h3eb3e6f68ba8a062@mail.gmail.com> (raw)
In-Reply-To: <200608262143.37390.len.brown@intel.com>

On 8/26/06, Len Brown <len.brown@intel.com> wrote:
> On Saturday 26 August 2006 20:21, Om Narasimhan wrote:
> > Hi,
> > This patch fixes one memory leak in drivers/acpi/acpi_memhotplug.c
> > Replaces all kmalloc() calls succeeded by memset() to kzalloc() calls.
> > Applies cleanly to 2.6.18-rc4. Compile tested.
>
> Compile testing is more effective is you use a .config that
> builds each of the source files changed.
I have compiled it with .config files resulting from targets
'allmodconfig' and 'allyesconfig'.
> > diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> > index b0d4b14..eb8a5da 100644
> > --- a/drivers/acpi/acpi_memhotplug.c
> > +++ b/drivers/acpi/acpi_memhotplug.c
> > @@ -297,6 +297,7 @@ static int acpi_memory_disable_device(st
> >        * Ask the VM to offline this memory range.
> >        * Note: Assume that this function returns zero on success
> >        */
> > +     struct acpi_memory_info *info, *n;
>
> What tree is this patch against?
> This line is already present (above the comment) in 2.6.18-rc4.
This surprises me. This patch is against 2.6.18-rc4, git-pull -ed today morning.
Maybe I should do one more git-pull?

Thanks,
Om N

  reply	other threads:[~2006-08-27  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27  0:21 memory leak fix in acpi_memhotplug.c, kmalloc to kzalloc conversion Om Narasimhan
2006-08-27  1:43 ` Len Brown
2006-08-27  4:06   ` Om Narasimhan [this message]
2006-08-27  4:30     ` Om Narasimhan

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=6b4e42d10608262106ibc44172h3eb3e6f68ba8a062@mail.gmail.com \
    --to=om.turyx@gmail.com \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.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