From: Len Brown <lenb@kernel.org>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH]: ACPI: Change the array size from 5 to 8 for acpi_bus_id
Date: Thu, 21 May 2009 14:26:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0905211425390.4390@localhost.localdomain> (raw)
In-Reply-To: <1242894335.8523.61.camel@localhost.localdomain>
what bad things happen if this patch is not applied --
do some of those strcpy()'s overflow?
what good things happen if it is applied?
are you just eating up the padding because it is there?
thanks,
Len Brown, Intel Open Source Technology Center
On Thu, 21 May 2009, yakui_zhao wrote:
> From: Zhao Yakui <yaui.zhao@intel.com>
>
> In fact the following three bytes can't be used when the following data
> type is unsigned long or unsigned long long.
>
> Change the array size from 5 to 8 for the acpi_bus_id.
>
> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
> ---
> include/acpi/acpi_bus.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6/include/acpi/acpi_bus.h
> ===================================================================
> --- linux-2.6.orig/include/acpi/acpi_bus.h 2009-04-20 09:13:42.000000000 +0800
> +++ linux-2.6/include/acpi/acpi_bus.h 2009-05-21 16:18:25.000000000 +0800
> @@ -168,7 +168,7 @@
>
> /* Plug and Play */
>
> -typedef char acpi_bus_id[5];
> +typedef char acpi_bus_id[8];
> typedef unsigned long acpi_bus_address;
> typedef char acpi_hardware_id[15];
> typedef char acpi_unique_id[9];
>
>
> --
> 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:[~2009-05-21 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 8:25 [PATCH]: ACPI: Change the array size from 5 to 8 for acpi_bus_id yakui_zhao
2009-05-21 18:26 ` Len Brown [this message]
2009-05-21 19:07 ` Matthew Garrett
2009-05-22 2:08 ` yakui_zhao
2009-05-27 3:55 ` Len Brown
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.LFD.2.00.0905211425390.4390@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=yakui.zhao@intel.com \
/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