All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <torque@ukrpost.net>
To: "Luiz Fernando N. Capitulino" <lcapitulino@prefeitura.sp.gov.br>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, dely.l.sy@intel.com
Subject: Re: [PATCH] 2.6.6 memory allocation checks in drivers/pci/hotplug/shpchprm_acpi.c
Date: Tue, 08 Jun 2004 09:14:40 +0300	[thread overview]
Message-ID: <1086675280.2818.4.camel@firefly> (raw)
In-Reply-To: <20040607173552.GC2413@tirion.prodam>

On Mon, 2004-06-07 at 20:35, Luiz Fernando N. Capitulino wrote:
>  Hello Randy, Yury,
> 
> Em Sun, Jun 06, 2004 at 10:51:06AM -0700, Randy.Dunlap escreveu:
> 
> | On Sun, 06 Jun 2004 19:20:51 +0300 Yury Umanets wrote:
> | 
> | | Adds memory allocation checks in acpi_get__hpp()
> | | 
> | |  ./linux-2.6.6-modified/drivers/pci/hotplug/shpchprm_acpi.c |    2 ++
> | |  1 files changed, 2 insertions(+)
> | | 
> | | Signed-off-by: Yury Umanets <torque@ukrpost.net>
> | | 
> | | diff -rupN ./linux-2.6.6/drivers/pci/hotplug/shpchprm_acpi.c
> | | ./linux-2.6.6-modified/drivers/pci/hotplug/shpchprm_acpi.c
> | | --- ./linux-2.6.6/drivers/pci/hotplug/shpchprm_acpi.c	Mon May 10
> | | 05:32:28 2004
> | | +++ ./linux-2.6.6-modified/drivers/pci/hotplug/shpchprm_acpi.c	Wed Jun 
> | | 2 14:28:07 2004
> | | @@ -218,6 +218,8 @@ static void acpi_get__hpp ( struct acpi_
> | |  	}
> | |  
> | |  	ab->_hpp = kmalloc (sizeof (struct acpi__hpp), GFP_KERNEL);
> | | +	if (!ab->_hpp)
> | | +		goto free_and_return;
> | |  	memset(ab->_hpp, 0, sizeof(struct acpi__hpp));
> | |  
> | |  	ab->_hpp->cache_line_size	= nui[0];
> | | 
> | | -- 
> | 
> | All other failure paths in this function use err() to inform the
> | console about what's happening...  so flip a coin, I guess:
> | add a message or say that ACPI already has too many messages.  :(
> 
>  I sent the same patch for this some weeks ago. Dely accepted, but it was
> not applyed. Don't know why.
Hello,

I'm not sure that I know the order of patches reviewing/applying, but it
seems to be depend on contact person busyness and importance of the
patch. This patch is not so important though :)

-- 
umka


  reply	other threads:[~2004-06-08  6:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-06 16:20 [PATCH] 2.6.6 memory allocation checks in drivers/pci/hotplug/shpchprm_acpi.c Yury Umanets
2004-06-06 17:51 ` Randy.Dunlap
2004-06-07 15:52   ` Yury Umanets
2004-06-07 17:35   ` Luiz Fernando N. Capitulino
2004-06-08  6:14     ` Yury Umanets [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07 17:56 Sy, Dely L
2004-06-07 18:12 ` Greg KH
2004-06-07 18:27 Sy, Dely L

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=1086675280.2818.4.camel@firefly \
    --to=torque@ukrpost.net \
    --cc=akpm@osdl.org \
    --cc=dely.l.sy@intel.com \
    --cc=lcapitulino@prefeitura.sp.gov.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.